Скачать или смотреть Why PostgreSQL Was Written in C and Not C+ + : A Deep Dive into History and Performance

Discover why PostgreSQL, along with many other major databases, was developed in `C` instead of `C+ + `. Explore the historical context and performance considerations behind this important design choice.
---
This video is based on the question https://stackoverflow.com/q/66196196/ asked by the user 'user8152154' ( https://stackoverflow.com/u/8152154/ ) and on the answer https://stackoverflow.com/a/66196273/ provided by the user 'Thomas' ( https://stackoverflow.com/u/14637/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: why postgres written by c not c+ + ? is c has better performance or just a history reason?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Why PostgreSQL Was Written in C and Not C+ +

As a developer diving into the world of databases, you might find yourself wondering why certain systems, like PostgreSQL, are written in C rather than C+ + . Is it simply a matter of historical choice, or does performance play a significant role in this decision? In this guide, we will explore these questions, delving into PostgreSQL's unique history and the implications of language choice on performance.

The Historical Context of PostgreSQL

PostgreSQL has an inspiring backstory that sheds light on its programming language choice. Here's a brief overview:

Early Beginnings: PostgreSQL originated as a successor to the Ingres database in the 1970s. The groundwork for what would become PostgreSQL was laid long before C+ + was even established.

First Release: The first public version of PostgreSQL was released in 1996, but the idea and research around it began as early as 1986, around the same time as the release of The C+ + Programming Language by Bjarne Stroustrup.

Lack of C+ + During Development: During the development of the initial PostgreSQL versions, C+ + did not yet have widespread implementation or stability. Consequently, the developers chose C, a language that was well-established and widely used for system-level programming.

Performance Considerations

While historical factors are essential in understanding the language choice for PostgreSQL, let's delve into whether performance considerations also played a role.

Advantages of C Over C+ +

Lower-level Control:

C provides greater control over system resources and memory management compared to C+ + . This can lead to better optimization, especially in a high-performance database environment where resource management is critical.

Simplicity and Efficiency:

The simplicity of C reduces overhead in terms of features, enabling faster compilation and execution times.

Fewer Abstractions:

C allows developers to write closer to the hardware, which can lead to more efficient code for data-intensive applications like databases.

Stability and Predictability:

C has a history of stability; it is a well-known quantity in systems programming. C+ + introduces additional features, such as object-oriented programming, which could lead to complexity and unpredictable performance.

Historical Legacy

Legacy Code: Once a substantial amount of code is written in C, it creates a legacy that developers may be hesitant to refactor into C+ + , especially when performance and efficiency continue to meet the project's needs.

Compatibility: The first version's choice of language sets a precedent that influences future development. Maintaining consistency in language use simplifies maintenance and collaboration among developers.

Conclusion

In summary, the decision to use C for PostgreSQL instead of C+ + is deeply rooted in historical choices and performance considerations. At the time of its development, C was a stable, efficient, and widely understood language, while C+ + was still in its nascent stages. Today, this choice continues to impact the architecture and performance of PostgreSQL, contributing to its status as one of the world's most popular databases.

Whether you are exploring PostgreSQL's source code or considering which database technology to adopt, understanding the reasoning behind these historical decisions can enhance your appreciation of database management systems. Happy coding!