A meeting of the most active PostgreSQL developers is being planned for Wednesday 22nd May, 2013 near the University of Ottawa, prior to pgCon 2013. In order to keep the numbers manageable, this meeting is '''by invitation only'''. Unfortunately it is quite possible that we've overlooked important code developers during the planning of the event - if you feel you fall into this category and would like to attend, please contact Dave Page (dpage@pgadmin.org).

Please note that this year the attendee numbers have been kept low in order to keep the meeting more productive. Invitations have been sent only to developers that have been highly active on the database server over the 9.3 release cycle. We have not invited any contributors based on their contributions to related projects, or seniority in regional user groups or sponsoring companies, unlike in previous years.

This is a PostgreSQL Community event. Room and refreshments/food sponsored by EnterpriseDB. Other companies sponsored attendance for their developers.

== Time & Location ==

The meeting will be from 8:30AM to 5PM, and will be in the "Red Experience" room at:

Novotel Ottawa
33 Nicholas Street
Ottawa
Ontario
K1N 9M7

Food and drink will be provided throughout the day, including breakfast from 8AM.

[http://maps.google.ca/maps?f=q&source=s_q&hl=en&geocode=&q=novotel+ottawa&aq=&sll=49.891235,-97.15369&sspn=36.237851,79.013672&ie=UTF8&hq=novotel+ottawa&hnear=&ll=45.421528,-75.683699&spn=0.036869,0.077162&z=14&iwloc=A&layer=c&cbll=45.425741,-75.689638&panoid=Z4FUGnkZkdHAOkIxyjjS9Q&cbp=12,25.83,,0,-0.6 View on Google Maps]

== Attendees ==

The following people have RSVPed to the meeting (in alphabetical order, by surname):

* Josh Berkus (secretary)
* Jeff Davis
* Andrew Dunstan
* Peter Eisentraut
* Dimitri Fontaine
* Andres Freund
* Stephen Frost
* Peter Geoghegan
* Kevin Grittner
* Robert Haas
* Magnus Hagander
* Alexander Korotkov
* Fujii Masao
* Noah Misch
* Bruce Momjian
* Tom Lane
* Dave Page (chair)
* Simon Riggs
* KaiGai Kohei

== Proposed Agenda Items ==

Please list proposed agenda items here:

* 9.4 Commitfest schedule
* [http://wiki.postgresql.org/wiki/Parallel_Query_Execution Parallel Query Execution] (Bruce, Noah)
* logical changeset generation review & integration (Andres)
* utilization of upcoming non-volatile RAM device (Kaigai)
* pluggable plan/exec nodes (Kaigai)
** to offload targetlist calculation, sorting, aggregates, ...
* [[GIN generalization]] (Alexander)
* An Extensibility Roadmap (dim)
* Representing severity - derive severity from SQLSTATE (Peter Geoghegan - see http://www.postgresql.org/message-id/CA+TgmoZEjq7va+SfDZQwk6E4emEWThENNyxfqEGhB3iuoT1OJw@mail.gmail.com)
* Error logging infrastructure - store normalized statistics about errors in a circular buffer (Peter Geoghegan). Arguably this could be discussed alongside SQLSTATE item.

== Agenda ==

{| border="1" cellpadding="4" cellspacing="0"
!Time
!Item
!Presenter
|- style="font-style:italic;background-color:lightgray;"
|08:00
|Breakfast
|

|- style="font-style:italic;background-color:lightgray;"
|08:30 - 08:45
|Welcome and introductions
|Dave Page

|-
|08:45 - 09:45
|Parallel Query Execution
|Bruce/Noah

|-
|09:45 - 10:30
|Logical changeset generation review & integration
|Andres

|- style="font-style:italic;background-color:lightgray;"
|10:30 - 10:45
|Coffee break
|

|-
|10:45 - 11:00
|Utilization of upcoming non-volatile RAM devices
|KaiGai

|-
|11:00 - 11:30
|Pluggable plan/exec nodes
|KaiGai

|-
|11:30 - 11:50
|Representing severity
|Peter G.

|-
|11:50 - 12:30
|Error logging infrastructure
|Peter G.

|- style="font-style:italic;background-color:lightgray;"
|12:30 - 13:30
|Lunch
|

|-
|13:30 - 14:15
|GIN generalization
|Alexander

|-
|14:15 - 15:00
|An Extensibility Roadmap
|Dimitri

|- style="font-style:italic;background-color:lightgray;"
|15:00 - 15:15
|Tea break
|

|-
|15:15 - 15:30
|9.4 Commitfest schedule
|All

|-
|15:30 - 16:45
|Goals, priorities, and resources for 9.4
|All

|- style="font-style:italic;background-color:lightgray;"
|16:45 - 17:00
|Any other business/group photo
|Dave Page

|- style="font-style:italic;background-color:lightgray;"
|17:00
|Finish
|
|}

PgCon 2013 Developer Meeting

Dpage — Mon, 22 Apr 2013 16:39:19 GMT

Dpage: /* Attendees */

PostgreSQL Security Release Policy Draft

Dpage — Wed, 03 Apr 2013 08:12:34 GMT

Dpage: Correct version, remove "Windows" as installers cover multiple platforms, and stop inventing new acronyms.

= PostgreSQL Security Release Policy Draft =
Link: [http://www.postgresql.org/support/security/ http://www.postgresql.org/support/security/]

== Current ==

If you wish to report a new security vulnerability in PostgreSQL, please send an email to [mailto:security@postgresql.org security@postgresql.org]. For reporting non-security bugs, please see the [http://www.postgresql.org/support/submitbug Report a Bug] page.

PostgreSQL security updates are primarily made available as [http://www.postgresql.org/support/versioning minor version] upgrades. You are always advised to use the latest minor version available, as it will likely also contain other non-security related fixes. All known security issues are always fixed in the next major release, when it comes out.

PGDG believes that accuracy, completeness and availability of security information is essential for our users. We choose to pool all information on this one page, allowing easy searching for vulnerabilities by a range of criteria.

The following table lists all known security issues. Please note that versions prior to 8.3 are no longer supported and vulnerabilities for these versions may not be included in this list. New vulnerabilities in these versions are no longer patched.

Vulnerabilities list which major releases they were present in, and which version they are fixed in for each. If the vulnerability was exploitable without a valid login, this is also stated. They also list a vulnerability class, but we urge all users to read the description to determine if the bug affects specific installations or not.

(List of Security Issues + Fixes here)

== Draft ==

The PostgreSQL Global Development Group (PGDG) takes security seriously, allowing our users to place their trust in the web sites. applications and infrastructure built around PostgreSQL. Our approach covers fail-safe configuration options, a secure and robust database server as well as good integration with other security infrastructure software.

=== Reporting a Security Issue ===

If you wish to report a new security vulnerability in PostgreSQL, please send an email to our Security Team at [mailto:security@postgresql.org security@postgresql.org]. For reporting non-security bugs, please see the [http://www.postgresql.org/support/submitbug Report a Bug] page.

=== The Security Team ===

The PostgreSQL Security Team consists of a small number of committers and major contributors to PostgreSQL who work on resolving reported security issues. Members of the Security Team are appointed by the PostgreSQL Core Team, and serve until they resign or are removed for inactivity.

The Security Team attempts to resolve reported security issues as quickly as possible. Depending on the difficulty of the issue, it can take a few days to a few months to resolve. While known security issues are tracked by the Security Team, the list of pending issues is not available outside of the Team.

=== The Packagers List ===

The Packagers List consists of a few dozen people who create PostgreSQL packages for distribution to other users. This includes not only those who create the installers, RPMs, Debs, PPA, Ports and so forth, but also the engineers who do packaging for public Database-As-A-Service (DBaaS) clouds. If you feel that you belong on this list, but are not yet, please email pgsql-core@postgresql.org with a request to be included. This request should include:

* your full name
* your organization and/or company affiliation
* what platforms or DBaaS cloud you do packaging for
* your contact email
* names of existing trusted PostgreSQL community members who can give you a reference

For security reasons, the Packagers List needs to stay small, which means that requests which do not present a compelling reason to be on the list will be rejected.

In order to have packages prepared and ready to download on the day releases are announced, the Packagers list is given access to the source code of the PostgreSQL release 48 to 72 hours before release time.

=== Release Policy ===

PostgreSQL security updates are primarily made available as [http://www.postgresql.org/support/versioning minor version] upgrades. You are always advised to use the latest minor version available, as it will likely also contain other non-security related fixes. All known security issues are always fixed in the next major release, when it comes out.

=== Disclosure Timing ===

Security issues which are already known to the public or for which demonstrated exploits exist "in the wild" will be discussed, fixed, and patched in the open on the normal PostgreSQL git mirrors and mailing lists.

Minor security issues are handled simply by delaying commits until 72 hours before expected release time. This narrows the window between the disclosure of security issues in code and the availability of updated packages to one which we feel is reasonable and protects our users.

If an unpublished security issue is considered sufficiently serious by the Core Team, they will issue a public notice of the date of the upcoming security release one to two weeks before the release so that users can be prepared to update their installations as soon as the release is available. This notice will not contain any details of the security issue. The PostgreSQL main git repository will then be closed to the public for the approximately three days during which packages are being built, in order to avoid premature disclosure. Criteria for seriousness in a security issue includes the number of users likely to be affected, the potential damage from exploits, and the level of existing access and knowledge required by an attacker.

At this time, we are unable to provide advance notice of security details or code to any PostgreSQL end-users or application vendors, regardless of deployment size. While we understand the desire of some end-users to have access to security information and in-progress patches as soon as they are available, we cannot put the majority of our users, who depend on packages and installers, at risk. The PostgreSQL Project may revisit this policy in the future as our resources and the general thinking around security disclosure evolve.

=== Supported Versions and Fixed Vulnerabilities ===

PGDG believes that accuracy, completeness and availability of security information is essential for our users. We choose to pool all information on this one page, allowing easy searching for vulnerabilities by a range of criteria.

The following table lists all known security issues. Please note that versions prior to 8.4 are no longer supported and vulnerabilities for these versions may not be included in this list. New vulnerabilities in these versions are no longer patched.

Vulnerabilities list which major releases they were present in, and which version they are fixed in for each. If the vulnerability was exploitable without a valid login, this is also stated. They also list a vulnerability class, but we urge all users to read the description to determine if the bug affects specific installations or not.

(List of fixes goes here)

PGDay NYC 2013 Talks

Dpage — Mon, 25 Mar 2013 18:05:07 GMT

Dpage:

= PGDay NYC 2013 Talks =

== Friday March 22nd, 2013 ==

=== Liberty Hall C ===

* [http://momjian.us/main/writings/pgsql/locking.pdf Understanding the Postgres Lock Manager (Bruce Momjian)]
* [http://plv8-talk.herokuapp.com/ Embracing the Web with JSON and PLV8 (Will Leinweber)]

=== Liberty Hall A ===

* [[:File:PPCD.pdf|Postgres Plus Cloud Database (Dave Page)]]

[[Category:PostgreSQL Events]]

File:PPCD.pdf

Dpage — Mon, 25 Mar 2013 18:03:20 GMT

Dpage: Postgres Plus Cloud Database enables you to quickly and cheaply deploy self-healing, elastic, highly available PostgreSQL or Postgres Plus Advanced Server database clusters in cloud and virtualised environments, such as Amazon AWS. In this talk we'll look at the features offered, including: - Storage scaling and auto scale-out - Load balancing and high availability - Backup and cloning - Server configurability

Postgres Plus Cloud Database enables you to quickly and cheaply deploy self-healing, elastic, highly available PostgreSQL or Postgres Plus Advanced Server database clusters in cloud and virtualised environments, such as Amazon AWS.

In this talk we'll look at the features offered, including:

- Storage scaling and auto scale-out
- Load balancing and high availability
- Backup and cloning
- Server configurability

PgCon 2013 Developer Meeting

Dpage — Fri, 22 Mar 2013 11:05:58 GMT

Dpage: /* Attendees */

Dpage — Tue, 08 Nov 2011 10:07:39 GMT

Dpage: /* Ams 2 */

= PostgreSQL Conference Europe 2011 Talks =

== Talks: Wednesday 19th October, 2011 ==

=== Ams 1 ===
* [[Media:Mohan_PGCon_Keynote_10-19-2011.pdf|Ram Mohan Keynote: Afilias Winning Bet on Open Source]]
* [http://www.oslandia.com/files/1646fd60f9b0a4558d1e256cf3264572/pgconfeu2011_vincent_picavet_postgis.pdf Vincent Picavet - Geo in your database : Postgis]
* Heralding the Death of nosql — Will Leinweber, Heroku — http://pgeu-plv8.herokuapp.com
* [http://scanningpages.wordpress.com/?attachment_id=420| Slony Troubleshooting - Steve Singer, Afilias ]

=== Ams 2 ===
* [http://www.mgrid.net/blogs/mgrid-at-pgdayeu-2011 Yeb Havinga: Introducing ISO-21090 Healthcare Datatypes]
* [http://wiki.postgresql.org/images/d/df/Center_of_your_dataverse_PGCONFEU2011.pdf Dave Page: PostgreSQL at the centre of your dataverse]
* [http://ora2pg.darold.net/ora2pg-best-practices.pdf Gilles Darold: Best practices with Ora2Pg]

=== Ams 3 ===

* [http://www.hagander.net/talks/PostgreSQL%209.1%20-%20What's%20new.pdf Magnus Hagander, PostgreSQL 9.1 - What's New]
* [[Media:Ciolli-window-2011.pdf|Gianni Ciolli, Look Out The Window Functions (and free your SQL)]]
** plus four 2D heat diffusion movies, with different starting scenarios: [http://vimeo.com/30797130 a hot point],
** [http://vimeo.com/30797509 a hot segment],
** [http://vimeo.com/30797715 a hot square] and
** [http://vimeo.com/30797797 a cold square].
* [http://momjian.us/main/presentations/internals.html#optimizer Explaining the Postgres Query Optimizer]
* [http://www.2ndquadrant.com/static/2quad/media/pdfs/talks/SyncRepDurability.pdf Simon Riggs and Greg Smith: Synchronous Replication and Durability Tuning]
* [[Media:Smartgrid_for_the_datacenter_web.pdf|Stefan Kaltenbrunner, A smartgrid for the datacenter]]

== Talks: Thursday 20th October, 2011 ==

=== Ams 1 ===

* [[Media:slony1-2.1_londiste3.pdf|Cédric Villemain: londiste 3 et slony 2.1 ]]

* A Postgres Service (Peter van Hardenberg, Heroku) http://pgconfeu11-service.herokuapp.com/

* [[Media:SSI-PGConfEU2011.pdf|Heikki Linnakangas: Serializable Snapshot Isolation ]]

* [[Media:Fast_GiST_index_build.pdf|Alexander Korotkov: Fast GiST index build ]]

* [[Media:pgconf2011.eu-berg-pgapt.pdf|Christoph Berg: Connecting the Debian and PostgreSQL worlds ]]

=== Ams 2 ===
* [[Media:using-extensions.pdf|Dimitri Fontaine: Extensions are good for business logic]]
* Exposing the Power of Postgres to Ruby — Will Leinweber, Heroku — http://pgeu-ruby.herokuapp.com
* [http://wiki.postgresql.org/images/e/e6/Django-extensions.pdf Jonathan S. Katz: Writing Django Extensions for PostgreSQL]
* [[Media:Pgconf-2011-mysql-to-pg-print.pdf|Andreas 'ads' Scherbaum: Port databases from MySQL to PostgreSQL]]

=== Ams 3 ===
* [http://www.2ndquadrant.com/static/2quad/media/pdfs/talks/ImprovingVACUUMSuction.pdf Greg Smith: Improving VACUUM Suction]
* [[Media:Ciolli-debug-wcte-2011.pdf|Gianni Ciolli, Debug complex SQL queries with writable CTEs]]
* [[Media:pgconfeu_stats.odp|Guillaume Lelarge, What use are the statistics views?]]
* Lightning talk: [[Media:Ciolli-waiting-for-the-barman-2011.pdf|Gabriele Bartolini and Gianni Ciolli, waiting for (the) BaRMan]]

== Talks: Friday 21st October, 2011 ==

=== Ams 1 ===
* Reliable Databases in The Cloud with WAL-E (redux) - Dan Farina, Heroku - http://wal-e-pgeu2011.herokuapp.com/
* [http://wiki.postgresql.org/images/4/46/Knn.pdf Jonathan S. Katz: Accelerating Local Search With PostgreSQL 9.1]

=== Ams 2 ===

* [http://bunsen.credativ.com/~mme/2011/PGConf_EU.pdf Michael Meskes: Mission Impossible?]

=== Ams 3 ===
* [http://www.2ndquadrant.com/static/2quad/media/pdfs/talks/bottom-up-benchmarking-2011.pdf Greg Smith: Bottom-Up Database Benchmarking]
* [http://www.hagander.net/talks/The%20PostgreSQL%20Replication%20Protocol%20pgopen.pdf Magnus Hagander: The PostgreSQL Replication Protocol, Tools and Opportunities]
* [http://wiki.postgresql.org/images/f/fa/Pg-eu-2011-closing-keynote.pdf Bruce Momjian: Closing Keynote]

[[Category:PostgreSQL Europe]]

File:Center of your dataverse PGCONFEU2011.pdf

Dpage — Tue, 08 Nov 2011 10:06:01 GMT

Dpage: PostgreSQL at the center of your dataverse, presented at PGConf.EU 2011

PostgreSQL at the center of your dataverse, presented at PGConf.EU 2011

PGBR 2011, São Paulo

Dpage — Tue, 08 Nov 2011 10:02:29 GMT

Dpage:

* [http://wiki.postgresql.org/images/d/d3/Center_of_your_dataverse_PGBR2011.pdf PostgreSQL at the centre of your dataverse] (Dave Page)