2ndQuadrant is now part of EDB

Bringing together some of the world's top PostgreSQL experts.

2ndQuadrant | PostgreSQL
Mission Critical Databases
  • Contact us
  • EN
    • FR
    • IT
    • ES
    • DE
    • PT
  • Support & Services
  • Products
  • Downloads
    • Installers
      • Postgres Installer
      • 2UDA – Unified Data Analytics
    • Whitepapers
      • Business Case for PostgreSQL Support
      • Security Best Practices for PostgreSQL
    • Case Studies
      • Performance Tuning
        • BenchPrep
        • tastyworks
      • Distributed Clusters
        • ClickUp
        • European Space Agency (ESA)
        • Telefónica del Sur
        • Animal Logic
      • Database Administration
        • Agilis Systems
      • Professional Training
        • Met Office
        • London & Partners
      • Database Upgrades
        • Alfred Wegener Institute (AWI)
      • Database Migration
        • International Game Technology (IGT)
        • Healthcare Software Solutions (HSS)
        • Navionics
  • Postgres Learning Center
    • Webinars
      • Upcoming Webinars
      • Webinar Library
    • Whitepapers
      • Business Case for PostgreSQL Support
      • Security Best Practices for PostgreSQL
    • Blog
    • Training
      • Course Catalogue
    • Case Studies
      • Performance Tuning
        • BenchPrep
        • tastyworks
      • Distributed Clusters
        • ClickUp
        • European Space Agency (ESA)
        • Telefónica del Sur
        • Animal Logic
      • Database Administration
        • Agilis Systems
      • Professional Training
        • Met Office
        • London & Partners
      • Database Upgrades
        • Alfred Wegener Institute (AWI)
      • Database Migration
        • International Game Technology (IGT)
        • Healthcare Software Solutions (HSS)
        • Navionics
    • Books
      • PostgreSQL 11 Administration Cookbook
      • PostgreSQL 10 Administration Cookbook
      • PostgreSQL High Availability Cookbook – 2nd Edition
      • PostgreSQL 9 Administration Cookbook – 3rd Edition
      • PostgreSQL Server Programming Cookbook – 2nd Edition
      • PostgreSQL 9 Cookbook – Chinese Edition
    • Videos
    • Events
    • PostgreSQL
      • PostgreSQL – History
      • Who uses PostgreSQL?
      • PostgreSQL FAQ
      • PostgreSQL vs MySQL
      • The Business Case for PostgreSQL
      • Security Information
      • Documentation
  • About Us
    • About 2ndQuadrant
    • 2ndQuadrant’s Passion for PostgreSQL
    • News
    • Careers
    • Team Profile
  • Blog
  • Menu Menu
You are here: Home1 / Blog2 / Craig's PlanetPostgreSQL3 / Help us make a better PostgreSQL 9.3!
craig.ringer

Help us make a better PostgreSQL 9.3!

January 21, 2013/9 Comments/in Craig's PlanetPostgreSQL /by craig.ringer

As interest in PostgreSQL grows, so does the rate at which new patches are proposed. To maintain the high level of quality in PostgreSQL it is important that all patches be checked and reviewed, so that what gets added to the codebase is good quality.

Some of this evaluation requires a lot of expertise in the PostgreSQL core code, but most of it requires little development experience at all. The more initial checking and review gets done before patches get evaluated by the experts, the less work those experts have to do. So: please step up and review a patch. There are patch review guidelines on the wiki, and it’s quite an accessible process. Step right up if you want to contribute a little back to the software you use and rely on, or if there’s a particular enhancement you want to make sure goes into 9.3.

If you don’t feel up to reviewing the feature you’re interested in, you can still help by testing and initially reviewing something else, so others have more time to examine the complicated stuff. You can still help out.

I’ll be posting a series on patches proposed for 9.3, starting with today’s patch, Peter Eisentraut’s addition of a ALTER ROLE extension to change PostgreSQL settings (like work_mem, search_path, etc) for all users on all databases. The initial post explaining the patch is here and this is the commitfest entry.

To get involved, visit the current commitfest page, sign in with your PostgreSQL community login, and have a look at the list of patches needing review. If there’s one there that doesn’t have an existing reviewer listed, or that interests you, please get involved! Grab the patch, read the reviewer guidelines, and help make PostgreSQL better.

Share this entry
  • Share on Facebook
  • Share on Twitter
  • Share on WhatsApp
  • Share on LinkedIn
9 replies
  1. Daniël van Eeden
    Daniël van Eeden says:
    January 21, 2013 at 10:33 am

    I guess the “patch review guidelines on the wiki” link should point to https://wiki.postgresql.org/wiki/Reviewing_a_Patch ?

    Reply
    • craig.ringer
      craig.ringer says:
      January 21, 2013 at 10:35 am

      Thankyou; corrected. “” isn’t a particularly useful link…

      Reply
    • craig.ringer
      craig.ringer says:
      January 21, 2013 at 10:35 am

      Thankyou for reviewing this post 😉

      Reply
  2. Ian Barwick
    Ian Barwick says:
    January 21, 2013 at 10:45 pm

    Thanks for that, I’ve been looking for things to do but haven’t been sure where to start.

    Reply
  3. Username*
    Username* says:
    January 22, 2013 at 2:50 pm

    Has the group ever considered making use of something like this http://www.reviewboard.org/ to possibly help stream line the code review process?

    Reply
    • greg.smith
      greg.smith says:
      February 5, 2013 at 6:03 pm

      A few of us in the PostgreSQL community have looked at software like Review Board before. A related regular discussion point is using formal bug tracking software.

      The PostgreSQL developers are very oriented around using e-mail and traditional code editors for their work. Many of the people doing review start by reading the patch in their editor of choice, customized the way they want. The small CommitFest app works in terms of the message ids used for discussion. It’s not clear that Review Board helps out the people doing the majority of the work enough to justify using it yet. It would need to patched to have a similar level of integration with the PostgreSQL archives to make a lot of people happy. Certainly possible and maybe useful, but it’s not seen as a highly valuable project to most reviewers.

      Reply
  4. Jared
    Jared says:
    August 25, 2013 at 3:27 pm

    Is there a dead-simple tutorial on how to build postgresql for a commitfest and to apply a patch to make sure the patch 1. builds, 2. behaves as intended. (I saw this as the easiest and lowest hanging fruits people can do to help out the project (for non programmers))?

    eg) building postgresql so that it does not affect your primary installation etc..

    Reply
    • craig.ringer
      craig.ringer says:
      August 27, 2013 at 7:35 am

      The patch review guidelines on the wiki are the main resource right now, but you’re right that it’d be good to have something explaining how to build and run a test copy of Pg that doesn’t tread on the toes of anything already running. Added to my blog queue.

      Reply
    • craig.ringer
      craig.ringer says:
      September 2, 2013 at 6:59 am

      I hope this post – and the comments – help: https://blog.2ndquadrant.com/help-us-make-a-better-postgresql-9-3/

      Reply

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Search

Get in touch with us!

Recent Posts

  • Random Data December 3, 2020
  • Webinar: COMMIT Without Fear – The Beauty of CAMO [Follow Up] November 13, 2020
  • Full-text search since PostgreSQL 8.3 November 5, 2020
  • Random numbers November 3, 2020
  • Webinar: Best Practices for Bulk Data Loading in PostgreSQL [Follow Up] November 2, 2020

Featured External Blogs

Tomas Vondra's Blog

Our Bloggers

  • Simon Riggs
  • Alvaro Herrera
  • Andrew Dunstan
  • Craig Ringer
  • Francesco Canovai
  • Gabriele Bartolini
  • Giulio Calacoci
  • Ian Barwick
  • Marco Nenciarini
  • Mark Wong
  • Pavan Deolasee
  • Petr Jelinek
  • Shaun Thomas
  • Tomas Vondra
  • Umair Shahid

PostgreSQL Cloud

2QLovesPG 2UDA 9.6 backup Barman BDR Business Continuity community conference database DBA development devops disaster recovery greenplum Hot Standby JSON JSONB logical replication monitoring OmniDB open source Orange performance PG12 pgbarman pglogical PG Phriday postgres Postgres-BDR postgres-xl PostgreSQL PostgreSQL 9.6 PostgreSQL10 PostgreSQL11 PostgreSQL 11 PostgreSQL 11 New Features postgresql repmgr Recovery replication security sql wal webinar webinars

Support & Services

24/7 Production Support

Developer Support

Remote DBA for PostgreSQL

PostgreSQL Database Monitoring

PostgreSQL Health Check

PostgreSQL Performance Tuning

Database Security Audit

Upgrade PostgreSQL

PostgreSQL Migration Assessment

Migrate from Oracle to PostgreSQL

Products

HA Postgres Clusters

Postgres-BDR®

2ndQPostgres

pglogical

repmgr

Barman

Postgres Cloud Manager

SQL Firewall

Postgres-XL

OmniDB

Postgres Installer

2UDA

Postgres Learning Center

Introducing Postgres

Blog

Webinars

Books

Videos

Training

Case Studies

Events

About Us

About 2ndQuadrant

What does 2ndQuadrant Mean?

News

Careers 

Team Profile

© 2ndQuadrant Ltd. All rights reserved. | Privacy Policy
  • Twitter
  • LinkedIn
  • Facebook
  • Youtube
  • Mail
Cygwin users needed to test a patch for PostgreSQL 9.3 The first Australian PostgreSQL Day
Scroll to top
×