We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Michael Paquier: PostgreSQL hacker tips (PGConf.EU 2023)
Get insider tips from a seasoned PostgreSQL hacker on how to write better code, collaborate with the community, and streamline your development workflow.
-
Use
dot
files for convenient customization of development environment. - Perform recursive testing of Postgres for stable results.
-
Use
meson
andninja
instead ofconfigure
for build and testing. - Always test specific patches instead of relying on a single make check.
- Enforce consistency of code style and formatting through a centralized review process.
- Prioritize efficiency and simplicity in your work.
- Run individual queries and not a set of queries when testing code.
- Split your patch into multiple smaller patches for better understanding and feedback.
- Include all necessary changes and fixes in your patch.
- Ensure that your code works correctly with different versions of PostgreSQL and different environments.
-
Use
patch tracker
to manage your patches. - Don’t make changes without properly testing and debugging them.
- Communicate your changes and thoughts with the community and committee.
- Understand and respect the process and rules of PostgreSQL.
- Be cautious when committing code and consider the potential impact of your changes.
- Use hooks and other features to simplify your workflow.
- Run multiple build configurations and testing scenarios for your code.
-
Use
Git scripts
to automate your workflow. - Have a clear plan and direction for your work.
- Collaborate and contribute to the PostgreSQL community.