24th September 2020: PostgreSQL 13 Released!

Last Week to Participate in PostgreSQL Certification JTA Survey

Posted on 2008-11-08

Hello Everyone!

The PostgreSQL Certification JTA Survey currently underway is nearing its conclusion. The survey will close November 14th at which time the process of reviewing and analyzing the responses will begin. That leaves just under a week to give your thoughts on how a community driven certification should look.

We ask everyone that has not taken the survey to please take a few minutes and follow the instructions below to participate. It is only by your participation that the certification created by this project will be able provide real value to, and reflect the needs and desires of, the PostgreSQL community.

We thank everyone that has already taken the survey. Your answers will be very helpful in the next stage of this project.

How to Participate

To take the survey, please register at:


The registration process takes just a couple of minutes. Once registration is complete and you are logged in, click JTA in the menu followed by “participate in the survey” (http://www.postgresqlcertification.org/job_task_analysis). The survey takes approximately 30 minutes to complete.

Who Should Participate?

Everyone! The entire point of this project is to create a certification by and for the PostgreSQL Community. Do you know someone that uses or is considering using PostgreSQL or another database? Encourage them to participate in the survey as well.

About the PostgreSQL Certification Project

The primary focus of the PostgreSQL Certification Project is the creation and support of a community driven and endorsed series of tiered certifications that provide a standardized method of identifying the knowledge and skills of database professionals working with PostgreSQL.

For more information please visit the project’s site at http://www.postgresqlcertification.org.

If you are interested in joining the project you may subscribe to the project’s mailing list at:


This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.