https://wiki.postgresql.org/api.php?action=feedcontributions&user=Dsteele&feedformat=atomPostgreSQL wiki - User contributions [en]2024-03-28T19:25:45ZUser contributionsMediaWiki 1.35.13https://wiki.postgresql.org/index.php?title=Ecosystem:Backup&diff=38724Ecosystem:Backup2024-03-24T22:07:40Z<p>Dsteele: /* pgBackRest */</p>
<hr />
<div>== Amanda ==<br />
<br />
* Provider -- Zmanda, Inc., University of Maryland at College Park<br />
* Website -- http://www.amanda.org/<br />
* License -- open source (BSD-style, GPLv2) for Community Edition, and proprietary for Enterprise Edition<br />
* Interoperability level -- explicitly supports PostgreSQL 8.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- AMANDA, the Advanced Maryland Automatic Network Disk Archiver, is a backup system that allows the administrator of a LAN to set up a single master backup server to back up multiple hosts to a single large capacity tape or disk drive. Amanda uses native tools (such as GNUtar, dump) for backup and can back up a large number of workstations running multiple versions of Unix/Mac OS X/Linux/Windows.<br />
* Additional info -- [[Ecosystem:Amanda|click here]]<br />
<br />
== Bacula ==<br />
<br />
* Provider -- Kern Sibbald, Bacula Systems S.A.<br />
* Website -- https://www.bacula.org/<br />
* License -- open source (AGPLv3) for Community Edition, and proprietary for Enterprise Edition<br />
* Interoperability level -- explicitly supports PostgreSQL 7.4 or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Bacula is a set of Open Source, computer programs that permit you (or the system administrator) to manage backup, recovery, and verification of computer data across a network of computers of different kinds. Bacula is relatively easy to use and very efficient, while offering many advanced storage management features that make it easy to find and recover lost or damaged files. In technical terms, it is an Open Source, network based backup program. According to Source Forge statistics (rank and downloads), Bacula is by far the most popular Open Source backup program.<br />
* Additional info -- [[Ecosystem:Bacula|click here]]<br />
<br />
== Barman - Backup and Recovery Manager for PostgreSQL ==<br />
<br />
* Provider -- 2ndQuadrant<br />
* Website -- https://www.2ndquadrant.com/<br />
* License -- GPL v3<br />
* Interoperability level -- See: http://www.pgbarman.org/<br />
* Verified PostgreSQL versions -- https://www.2ndquadrant.com/en/resources/barman/<br />
* Last update (YYYY-MM-DD) -- 2020-07-09<br />
* Description -- Barman (Backup and Recovery Manager) is an open-source administration tool for disaster recovery of PostgreSQL databases with high business continuity requirements. Barman allows remote backups of multiple servers in business critical environments and helps DBAs during the recovery phase.<br />
* Additional info -- http://www.pgbarman.org/<br />
<br />
== Handy Backup ==<br />
<br />
* Provider -- Novosoft LLC<br />
* Website -- https://www.handybackup.net/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 9 or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Handy Backup is famous for being a Swiss Army Knife of data backup tools. Its functionality covers everything from files-based copying and disk imaging to multi-server backup.<br />
* Additional info -- [[Ecosystem:Handy Backup|click here]]<br />
<br />
== Iperius Backup ==<br />
<br />
* Provider -- Enter Srl<br />
* Website -- https://www.iperiusbackup.com/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL (no specific version is specified)<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Iperius Backup is a backup software for Windows. With the introduction of PostgreSQL backup, Iperius is now one of the best and most complete database backup software in the world: with a single license, the Advanced DB, you can back up unlimited servers and databases Oracle, SQL Server, PostgreSQL, MySQL and MariaDB. Moreover, you’ve other powerful features such as automatic compression, encryption, and automatic copy to any device (NAS, FTP server, Cloud, Google Drive, Amazon S3, etc.).<br />
* Additional info -- [[Ecosystem:Iperius Backup|click here]]<br />
<br />
== NetVault Backup ==<br />
<br />
* Provider -- Quest Software Inc.<br />
* Website -- https://www.quest.com/products/netvault-backup/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 8.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Protect data in diverse IT environments - from one intuitive console -- in this scalable backup and recovery solution. NetVault Backup supports multiple server and application platforms in both physical and virtual environments. That means you can ensure availability of business-critical applications, including Oracle, Exchange, MySQL, SQL Server, DB2, and SAP. With NetVault Backup, you can safeguard information stored on network-attached storage (NAS) devices. It also allows you to back up to tape or disk, as well as leverage data deduplication to minimize your storage footprint.<br />
* Additional info -- [[Ecosystem:NetVault Backup|click here]]<br />
<br />
== pg_probackup ==<br />
<br />
* Provider -- Postgres Professional<br />
* Website -- https://github.com/postgrespro/pg_probackup<br />
* License -- PostgreSQL License<br />
* Interoperability level -- >= 9.5 <br />
* Verified PostgreSQL versions -- >= 9.5<br />
* Last update (YYYY-MM-DD) -- 2019-08-13<br />
* Current Version: 2.3.1<br />
* Description -- pg_probackup is a feature-rich and simple to use utility to manage backup and recovery of PostgreSQL database clusters. It is designed to perform periodic backups of the PostgreSQL instance that enable you to restore the server in case of a failure.<br />
* Documentation -- https://postgrespro.github.io/pg_probackup/<br />
<br />
== pgBackRest ==<br />
<br />
* Provider -- pgBackRest Community, Crunchy Data<br />
* Website -- https://pgbackrest.org/<br />
* License -- MIT License<br />
* Interoperability level -- >= 9.4 <br />
* Verified PostgreSQL versions -- >= 9.4<br />
* Last update (YYYY-MM-DD) -- 2024-03-25<br />
* Current Version: 2.51<br />
* Description -- pgBackRest is a reliable backup and restore solution for PostgreSQL that seamlessly scales up to the largest databases and workloads<br />
* Documentation -- https://pgbackrest.org/<br />
<br />
== pgmoneta ==<br />
<br />
* Provider --pgmoneta community<br />
* Website -- https://github.com/pgmoneta/pgmoneta<br />
* License -- BSD 3-Clause License<br />
* Interoperability level -- >= 10 <br />
* Verified PostgreSQL versions -- >= 10<br />
* Last update (YYYY-MM-DD) -- 2022-09-22<br />
* Current Version: 0.6.0<br />
* Description -- pgmoneta is a backup / restore solution that supports on-disk encryption, storage engines, monitoring and symlinks.<br />
* Documentation -- https://pgmoneta.github.io/gettingstarted.html<br />
<br />
== Simpana ==<br />
<br />
* Provider -- Commvault<br />
* Website -- https://www.commvault.com/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 8.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Simpana software offers seamless and efficient backup and restore of data and information in your enterprise from any operating system, database, and application. Simpana software builds on this foundation by integrating application awareness with hardware snapshots, indexing, global deduplication, replication, search, and reporting, all within a single platform.<br />
* Additional info -- [[Ecosystem:Simpana|click here]]<br />
<br />
== Spectrum Protect ==<br />
<br />
* Provider -- IBM Corporation<br />
* Website -- https://www.ibm.com/us-en/marketplace/data-protection-and-recovery<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL (no specific version is specified)<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- IBM Spectrum Protect can simplify data protection where data is hosted in physical, virtual, software-defined or cloud environments. With IBM Spectrum Protect, you can choose the right software to manage and protect your data-while also simplifying backup administration, improving efficiencies, delivering scalable capacity and enabling advanced capabilities. With superior virtual machine (VM) protection, IBM Spectrum Protect integrates with IBM Spectrum Protect Plus for fast and easy VM protection with searchable catalog and role-based administration.<br />
* Additional info -- [[Ecosystem:Spectrum Protect|click here]]<br />
<br />
* Provider -- Spictera & IBM<br />
* Website -- https://www-356.ibm.com/partnerworld/gsd/solutiondetails.do?solution=56435&lc=en&stateCd=P&tab=2<br />
* Website -- https://www.suse.com/susePSC/viewVersionPage?versionID=20888<br />
* Website -- https://access.redhat.com/ecosystem/software/4167431<br />
* Website -- http://www.spictera.com<br />
* License -- proprietary<br />
* Interoperability -- generic data protection, supports any PostgreSQL version<br />
* Verified PostgreSQL versions -- PostgreSQL 8/9/10/11<br />
* Last update (YYYY-MM-DD) -- 2019-06-18<br />
* Description -- SPFS is a file system that makes it possible to mount IBM Spectrum Protect filespaces anywhere on your server. All file operations goes directly via the IBM Spectrum Protect Client API to the IBM Spectrum Protect backup server. It is very easy to integrate WAL backups, and one can use the prefered backup methods (pg_dump, pg_basebackup) or any other combinations that the PostgreSQL administrator has preferences of using. Very good data reduction ~75-85% using de-duplication in combination with compression, possible to encrypt data using private keys. Easy to use, requires almost no education.<br />
<br />
== Veritas NetBackup for PostgreSQL Agent ==<br />
<br />
* Provider -- Veritas<br />
* Website -- https://www.enterprisedb.com/blog/veritas-netbackup-and-edb-postgres<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 9.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2019-06-28<br />
* Description -- This is a PostgreSQL specific agent for NetBackup, the enterprise backup and recovery solution. It uses filesystem snapshot technology to take a cohesive backup of configured PG databases, rather than dump to an external file and backing that up. This (at least in theory) should mean backup and recovery are both efficient. The NetBackup documentation shows the agent as supported for Windows and Linux (RHEL, SLES)<br />
* Documentation -- https://www.veritas.com/content/support/en_US/doc/129277259-137906533-0/v129276450-137906533<br />
<br />
[[Category:Ecosystem:Backup]]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Ecosystem:Backup&diff=38599Ecosystem:Backup2024-01-25T13:37:20Z<p>Dsteele: /* pgBackRest */</p>
<hr />
<div>== Amanda ==<br />
<br />
* Provider -- Zmanda, Inc., University of Maryland at College Park<br />
* Website -- http://www.amanda.org/<br />
* License -- open source (BSD-style, GPLv2) for Community Edition, and proprietary for Enterprise Edition<br />
* Interoperability level -- explicitly supports PostgreSQL 8.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- AMANDA, the Advanced Maryland Automatic Network Disk Archiver, is a backup system that allows the administrator of a LAN to set up a single master backup server to back up multiple hosts to a single large capacity tape or disk drive. Amanda uses native tools (such as GNUtar, dump) for backup and can back up a large number of workstations running multiple versions of Unix/Mac OS X/Linux/Windows.<br />
* Additional info -- [[Ecosystem:Amanda|click here]]<br />
<br />
== Bacula ==<br />
<br />
* Provider -- Kern Sibbald, Bacula Systems S.A.<br />
* Website -- https://www.bacula.org/<br />
* License -- open source (AGPLv3) for Community Edition, and proprietary for Enterprise Edition<br />
* Interoperability level -- explicitly supports PostgreSQL 7.4 or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Bacula is a set of Open Source, computer programs that permit you (or the system administrator) to manage backup, recovery, and verification of computer data across a network of computers of different kinds. Bacula is relatively easy to use and very efficient, while offering many advanced storage management features that make it easy to find and recover lost or damaged files. In technical terms, it is an Open Source, network based backup program. According to Source Forge statistics (rank and downloads), Bacula is by far the most popular Open Source backup program.<br />
* Additional info -- [[Ecosystem:Bacula|click here]]<br />
<br />
== Barman - Backup and Recovery Manager for PostgreSQL ==<br />
<br />
* Provider -- 2ndQuadrant<br />
* Website -- https://www.2ndquadrant.com/<br />
* License -- GPL v3<br />
* Interoperability level -- See: http://www.pgbarman.org/<br />
* Verified PostgreSQL versions -- https://www.2ndquadrant.com/en/resources/barman/<br />
* Last update (YYYY-MM-DD) -- 2020-07-09<br />
* Description -- Barman (Backup and Recovery Manager) is an open-source administration tool for disaster recovery of PostgreSQL databases with high business continuity requirements. Barman allows remote backups of multiple servers in business critical environments and helps DBAs during the recovery phase.<br />
* Additional info -- http://www.pgbarman.org/<br />
<br />
== Handy Backup ==<br />
<br />
* Provider -- Novosoft LLC<br />
* Website -- https://www.handybackup.net/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 9 or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Handy Backup is famous for being a Swiss Army Knife of data backup tools. Its functionality covers everything from files-based copying and disk imaging to multi-server backup.<br />
* Additional info -- [[Ecosystem:Handy Backup|click here]]<br />
<br />
== Iperius Backup ==<br />
<br />
* Provider -- Enter Srl<br />
* Website -- https://www.iperiusbackup.com/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL (no specific version is specified)<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Iperius Backup is a backup software for Windows. With the introduction of PostgreSQL backup, Iperius is now one of the best and most complete database backup software in the world: with a single license, the Advanced DB, you can back up unlimited servers and databases Oracle, SQL Server, PostgreSQL, MySQL and MariaDB. Moreover, you’ve other powerful features such as automatic compression, encryption, and automatic copy to any device (NAS, FTP server, Cloud, Google Drive, Amazon S3, etc.).<br />
* Additional info -- [[Ecosystem:Iperius Backup|click here]]<br />
<br />
== NetVault Backup ==<br />
<br />
* Provider -- Quest Software Inc.<br />
* Website -- https://www.quest.com/products/netvault-backup/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 8.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Protect data in diverse IT environments - from one intuitive console -- in this scalable backup and recovery solution. NetVault Backup supports multiple server and application platforms in both physical and virtual environments. That means you can ensure availability of business-critical applications, including Oracle, Exchange, MySQL, SQL Server, DB2, and SAP. With NetVault Backup, you can safeguard information stored on network-attached storage (NAS) devices. It also allows you to back up to tape or disk, as well as leverage data deduplication to minimize your storage footprint.<br />
* Additional info -- [[Ecosystem:NetVault Backup|click here]]<br />
<br />
== pg_probackup ==<br />
<br />
* Provider -- Postgres Professional<br />
* Website -- https://github.com/postgrespro/pg_probackup<br />
* License -- PostgreSQL License<br />
* Interoperability level -- >= 9.5 <br />
* Verified PostgreSQL versions -- >= 9.5<br />
* Last update (YYYY-MM-DD) -- 2019-08-13<br />
* Current Version: 2.3.1<br />
* Description -- pg_probackup is a feature-rich and simple to use utility to manage backup and recovery of PostgreSQL database clusters. It is designed to perform periodic backups of the PostgreSQL instance that enable you to restore the server in case of a failure.<br />
* Documentation -- https://postgrespro.github.io/pg_probackup/<br />
<br />
== pgBackRest ==<br />
<br />
* Provider -- pgBackRest Community, Crunchy Data<br />
* Website -- https://pgbackrest.org/<br />
* License -- MIT License<br />
* Interoperability level -- >= 9.4 <br />
* Verified PostgreSQL versions -- >= 9.4<br />
* Last update (YYYY-MM-DD) -- 2024-01-22<br />
* Current Version: 2.50<br />
* Description -- pgBackRest is a reliable backup and restore solution for PostgreSQL that seamlessly scales up to the largest databases and workloads<br />
* Documentation -- https://pgbackrest.org/<br />
<br />
== pgmoneta ==<br />
<br />
* Provider --pgmoneta community<br />
* Website -- https://github.com/pgmoneta/pgmoneta<br />
* License -- BSD 3-Clause License<br />
* Interoperability level -- >= 10 <br />
* Verified PostgreSQL versions -- >= 10<br />
* Last update (YYYY-MM-DD) -- 2022-09-22<br />
* Current Version: 0.6.0<br />
* Description -- pgmoneta is a backup / restore solution that supports on-disk encryption, storage engines, monitoring and symlinks.<br />
* Documentation -- https://pgmoneta.github.io/gettingstarted.html<br />
<br />
== Simpana ==<br />
<br />
* Provider -- Commvault<br />
* Website -- https://www.commvault.com/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 8.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Simpana software offers seamless and efficient backup and restore of data and information in your enterprise from any operating system, database, and application. Simpana software builds on this foundation by integrating application awareness with hardware snapshots, indexing, global deduplication, replication, search, and reporting, all within a single platform.<br />
* Additional info -- [[Ecosystem:Simpana|click here]]<br />
<br />
== Spectrum Protect ==<br />
<br />
* Provider -- IBM Corporation<br />
* Website -- https://www.ibm.com/us-en/marketplace/data-protection-and-recovery<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL (no specific version is specified)<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- IBM Spectrum Protect can simplify data protection where data is hosted in physical, virtual, software-defined or cloud environments. With IBM Spectrum Protect, you can choose the right software to manage and protect your data-while also simplifying backup administration, improving efficiencies, delivering scalable capacity and enabling advanced capabilities. With superior virtual machine (VM) protection, IBM Spectrum Protect integrates with IBM Spectrum Protect Plus for fast and easy VM protection with searchable catalog and role-based administration.<br />
* Additional info -- [[Ecosystem:Spectrum Protect|click here]]<br />
<br />
* Provider -- Spictera & IBM<br />
* Website -- https://www-356.ibm.com/partnerworld/gsd/solutiondetails.do?solution=56435&lc=en&stateCd=P&tab=2<br />
* Website -- https://www.suse.com/susePSC/viewVersionPage?versionID=20888<br />
* Website -- https://access.redhat.com/ecosystem/software/4167431<br />
* Website -- http://www.spictera.com<br />
* License -- proprietary<br />
* Interoperability -- generic data protection, supports any PostgreSQL version<br />
* Verified PostgreSQL versions -- PostgreSQL 8/9/10/11<br />
* Last update (YYYY-MM-DD) -- 2019-06-18<br />
* Description -- SPFS is a file system that makes it possible to mount IBM Spectrum Protect filespaces anywhere on your server. All file operations goes directly via the IBM Spectrum Protect Client API to the IBM Spectrum Protect backup server. It is very easy to integrate WAL backups, and one can use the prefered backup methods (pg_dump, pg_basebackup) or any other combinations that the PostgreSQL administrator has preferences of using. Very good data reduction ~75-85% using de-duplication in combination with compression, possible to encrypt data using private keys. Easy to use, requires almost no education.<br />
<br />
== Veritas NetBackup for PostgreSQL Agent ==<br />
<br />
* Provider -- Veritas<br />
* Website -- https://www.enterprisedb.com/blog/veritas-netbackup-and-edb-postgres<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 9.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2019-06-28<br />
* Description -- This is a PostgreSQL specific agent for NetBackup, the enterprise backup and recovery solution. It uses filesystem snapshot technology to take a cohesive backup of configured PG databases, rather than dump to an external file and backing that up. This (at least in theory) should mean backup and recovery are both efficient. The NetBackup documentation shows the agent as supported for Windows and Linux (RHEL, SLES)<br />
* Documentation -- https://www.veritas.com/content/support/en_US/doc/129277259-137906533-0/v129276450-137906533<br />
<br />
[[Category:Ecosystem:Backup]]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Ecosystem:Backup&diff=38598Ecosystem:Backup2024-01-25T13:08:34Z<p>Dsteele: /* pgBackRest */</p>
<hr />
<div>== Amanda ==<br />
<br />
* Provider -- Zmanda, Inc., University of Maryland at College Park<br />
* Website -- http://www.amanda.org/<br />
* License -- open source (BSD-style, GPLv2) for Community Edition, and proprietary for Enterprise Edition<br />
* Interoperability level -- explicitly supports PostgreSQL 8.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- AMANDA, the Advanced Maryland Automatic Network Disk Archiver, is a backup system that allows the administrator of a LAN to set up a single master backup server to back up multiple hosts to a single large capacity tape or disk drive. Amanda uses native tools (such as GNUtar, dump) for backup and can back up a large number of workstations running multiple versions of Unix/Mac OS X/Linux/Windows.<br />
* Additional info -- [[Ecosystem:Amanda|click here]]<br />
<br />
== Bacula ==<br />
<br />
* Provider -- Kern Sibbald, Bacula Systems S.A.<br />
* Website -- https://www.bacula.org/<br />
* License -- open source (AGPLv3) for Community Edition, and proprietary for Enterprise Edition<br />
* Interoperability level -- explicitly supports PostgreSQL 7.4 or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Bacula is a set of Open Source, computer programs that permit you (or the system administrator) to manage backup, recovery, and verification of computer data across a network of computers of different kinds. Bacula is relatively easy to use and very efficient, while offering many advanced storage management features that make it easy to find and recover lost or damaged files. In technical terms, it is an Open Source, network based backup program. According to Source Forge statistics (rank and downloads), Bacula is by far the most popular Open Source backup program.<br />
* Additional info -- [[Ecosystem:Bacula|click here]]<br />
<br />
== Barman - Backup and Recovery Manager for PostgreSQL ==<br />
<br />
* Provider -- 2ndQuadrant<br />
* Website -- https://www.2ndquadrant.com/<br />
* License -- GPL v3<br />
* Interoperability level -- See: http://www.pgbarman.org/<br />
* Verified PostgreSQL versions -- https://www.2ndquadrant.com/en/resources/barman/<br />
* Last update (YYYY-MM-DD) -- 2020-07-09<br />
* Description -- Barman (Backup and Recovery Manager) is an open-source administration tool for disaster recovery of PostgreSQL databases with high business continuity requirements. Barman allows remote backups of multiple servers in business critical environments and helps DBAs during the recovery phase.<br />
* Additional info -- http://www.pgbarman.org/<br />
<br />
== Handy Backup ==<br />
<br />
* Provider -- Novosoft LLC<br />
* Website -- https://www.handybackup.net/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 9 or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Handy Backup is famous for being a Swiss Army Knife of data backup tools. Its functionality covers everything from files-based copying and disk imaging to multi-server backup.<br />
* Additional info -- [[Ecosystem:Handy Backup|click here]]<br />
<br />
== Iperius Backup ==<br />
<br />
* Provider -- Enter Srl<br />
* Website -- https://www.iperiusbackup.com/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL (no specific version is specified)<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Iperius Backup is a backup software for Windows. With the introduction of PostgreSQL backup, Iperius is now one of the best and most complete database backup software in the world: with a single license, the Advanced DB, you can back up unlimited servers and databases Oracle, SQL Server, PostgreSQL, MySQL and MariaDB. Moreover, you’ve other powerful features such as automatic compression, encryption, and automatic copy to any device (NAS, FTP server, Cloud, Google Drive, Amazon S3, etc.).<br />
* Additional info -- [[Ecosystem:Iperius Backup|click here]]<br />
<br />
== NetVault Backup ==<br />
<br />
* Provider -- Quest Software Inc.<br />
* Website -- https://www.quest.com/products/netvault-backup/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 8.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Protect data in diverse IT environments - from one intuitive console -- in this scalable backup and recovery solution. NetVault Backup supports multiple server and application platforms in both physical and virtual environments. That means you can ensure availability of business-critical applications, including Oracle, Exchange, MySQL, SQL Server, DB2, and SAP. With NetVault Backup, you can safeguard information stored on network-attached storage (NAS) devices. It also allows you to back up to tape or disk, as well as leverage data deduplication to minimize your storage footprint.<br />
* Additional info -- [[Ecosystem:NetVault Backup|click here]]<br />
<br />
== pg_probackup ==<br />
<br />
* Provider -- Postgres Professional<br />
* Website -- https://github.com/postgrespro/pg_probackup<br />
* License -- PostgreSQL License<br />
* Interoperability level -- >= 9.5 <br />
* Verified PostgreSQL versions -- >= 9.5<br />
* Last update (YYYY-MM-DD) -- 2019-08-13<br />
* Current Version: 2.3.1<br />
* Description -- pg_probackup is a feature-rich and simple to use utility to manage backup and recovery of PostgreSQL database clusters. It is designed to perform periodic backups of the PostgreSQL instance that enable you to restore the server in case of a failure.<br />
* Documentation -- https://postgrespro.github.io/pg_probackup/<br />
<br />
== pgBackRest ==<br />
<br />
* Provider -- David Steele, Crunchy Data<br />
* Website -- https://pgbackrest.org/<br />
* License -- MIT License<br />
* Interoperability level -- >= 9.4 <br />
* Verified PostgreSQL versions -- >= 9.4<br />
* Last update (YYYY-MM-DD) -- 2024-01-22<br />
* Current Version: 2.50<br />
* Description -- pgBackRest is a reliable backup and restore solution for PostgreSQL that seamlessly scales up to the largest databases and workloads<br />
* Documentation -- https://pgbackrest.org/<br />
<br />
== pgmoneta ==<br />
<br />
* Provider --pgmoneta community<br />
* Website -- https://github.com/pgmoneta/pgmoneta<br />
* License -- BSD 3-Clause License<br />
* Interoperability level -- >= 10 <br />
* Verified PostgreSQL versions -- >= 10<br />
* Last update (YYYY-MM-DD) -- 2022-09-22<br />
* Current Version: 0.6.0<br />
* Description -- pgmoneta is a backup / restore solution that supports on-disk encryption, storage engines, monitoring and symlinks.<br />
* Documentation -- https://pgmoneta.github.io/gettingstarted.html<br />
<br />
== Simpana ==<br />
<br />
* Provider -- Commvault<br />
* Website -- https://www.commvault.com/<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 8.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- Simpana software offers seamless and efficient backup and restore of data and information in your enterprise from any operating system, database, and application. Simpana software builds on this foundation by integrating application awareness with hardware snapshots, indexing, global deduplication, replication, search, and reporting, all within a single platform.<br />
* Additional info -- [[Ecosystem:Simpana|click here]]<br />
<br />
== Spectrum Protect ==<br />
<br />
* Provider -- IBM Corporation<br />
* Website -- https://www.ibm.com/us-en/marketplace/data-protection-and-recovery<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL (no specific version is specified)<br />
* Verified PostgreSQL versions -- didn't actually run the program, but just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2018-3-11<br />
* Description -- IBM Spectrum Protect can simplify data protection where data is hosted in physical, virtual, software-defined or cloud environments. With IBM Spectrum Protect, you can choose the right software to manage and protect your data-while also simplifying backup administration, improving efficiencies, delivering scalable capacity and enabling advanced capabilities. With superior virtual machine (VM) protection, IBM Spectrum Protect integrates with IBM Spectrum Protect Plus for fast and easy VM protection with searchable catalog and role-based administration.<br />
* Additional info -- [[Ecosystem:Spectrum Protect|click here]]<br />
<br />
* Provider -- Spictera & IBM<br />
* Website -- https://www-356.ibm.com/partnerworld/gsd/solutiondetails.do?solution=56435&lc=en&stateCd=P&tab=2<br />
* Website -- https://www.suse.com/susePSC/viewVersionPage?versionID=20888<br />
* Website -- https://access.redhat.com/ecosystem/software/4167431<br />
* Website -- http://www.spictera.com<br />
* License -- proprietary<br />
* Interoperability -- generic data protection, supports any PostgreSQL version<br />
* Verified PostgreSQL versions -- PostgreSQL 8/9/10/11<br />
* Last update (YYYY-MM-DD) -- 2019-06-18<br />
* Description -- SPFS is a file system that makes it possible to mount IBM Spectrum Protect filespaces anywhere on your server. All file operations goes directly via the IBM Spectrum Protect Client API to the IBM Spectrum Protect backup server. It is very easy to integrate WAL backups, and one can use the prefered backup methods (pg_dump, pg_basebackup) or any other combinations that the PostgreSQL administrator has preferences of using. Very good data reduction ~75-85% using de-duplication in combination with compression, possible to encrypt data using private keys. Easy to use, requires almost no education.<br />
<br />
== Veritas NetBackup for PostgreSQL Agent ==<br />
<br />
* Provider -- Veritas<br />
* Website -- https://www.enterprisedb.com/blog/veritas-netbackup-and-edb-postgres<br />
* License -- proprietary<br />
* Interoperability level -- explicitly supports PostgreSQL 9.x or later<br />
* Verified PostgreSQL versions -- didn't actually run the program, just checked the documentation<br />
* Last update (YYYY-MM-DD) -- 2019-06-28<br />
* Description -- This is a PostgreSQL specific agent for NetBackup, the enterprise backup and recovery solution. It uses filesystem snapshot technology to take a cohesive backup of configured PG databases, rather than dump to an external file and backing that up. This (at least in theory) should mean backup and recovery are both efficient. The NetBackup documentation shows the agent as supported for Windows and Linux (RHEL, SLES)<br />
* Documentation -- https://www.veritas.com/content/support/en_US/doc/129277259-137906533-0/v129276450-137906533<br />
<br />
[[Category:Ecosystem:Backup]]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=34115PostgreSQL 12 Open Items2019-09-27T19:20:34Z<p>Dsteele: /* Open Issues */</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please add new open items to the bottom of the list.<br />
<br />
* [https://www.postgresql.org/message-id/flat/5CF28EA0.80902%40anastigmatix.net Should we change jsonpath to avoid using standard syntax for not-quite-standard features?]<br />
** Additional discussion [https://www.postgresql.org/message-id/flat/CAPpHfdvDci4iqNF9fhRkTqhe-5_8HmzeLt56drH%2B_Rv2rNRqfg%40mail.gmail.com here]<br />
* [https://www.postgresql.org/message-id/CAHGQGwEYYg_Ng+03FtZczacCpYgJ2Pn=B_wPtWF+FFLYDgpa1g@mail.gmail.com After recovery starting when backup_label exists, but not recovery.signal shuts down, the restarted recovery doesn't enter an archive recovery mode and may fail.]<br />
* [https://www.postgresql.org/message-id/flat/e445616d-023e-a268-8aa1-67b8b335340c%40pgmasters.net Interaction of recovery target options with recovery.signal/standby.signal does not match documentation and includes some surprising behaviors.]<br />
<br />
== Older Bugs ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/15672-b9fa7db32698269f%40postgresql.org ATPostAlterTypeCleanup causes child indexes to be recreated with wrong relfilenode]<br />
** Crash/data corruption is fixed by {{PgCommitURL|02c359eeda50a71c951371c9d3e920ff8f514008}}<br />
** There's more to be done here, but it's not clear whether additional work is small enough to be in-scope for v11 or v12<br />
* [https://www.postgresql.org/message-id/15726-6d67e4fa14f027b3@postgresql.org parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker]<br />
* [https://www.postgresql.org/message-id/15746-6e0482a4c0f915cb@postgresql.org BUG #15746: cache lookup failed for function in plpgsql block]<br />
** This was already fixed in HEAD/v12 by a part of {{PgCommitURL|04fe805a1734eccd8dcdd34c8cc0ddcb62c7240c}}<br />
** Issue is whether it's worth the risk to back-patch unproven code<br />
* [https://www.postgresql.org/message-id/CA+hUKGKVWbz_iniqvFujPZLioFPxGwuVV6PJeeCrQ8SVcdg7FQ@mail.gmail.com Change resowner cleanup order for Windows?]<br />
* [https://www.postgresql.org/message-id/68d00017-ae5c-b14f-fc3a-c9e38e3ce792%40iki.fi B-Tree Page can become unrecyclable due to PageDeleteXid wraparound]<br />
** This was fixed in the new GiST page deletion by {{PgCommitURL|6655a7299d835dea9e8e0ba69cc5284611b96f29}}, but the same issue remains in B-tree.<br />
* [https://www.postgresql.org/message-id/17827.1549866683%40sss.pgh.pa.us Undesirable PANIC on snapshot file open failure]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAKcux6nZiO9-eEpr1ZD84bT1mBoVmeZkfont8iSpcmYrjhGWgA@mail.gmail.com getting ERROR "relation 16401 has no triggers" with partition foreign key alter]<br />
** Fixed in: {{PgCommitURL|5562272a4229cfa57354aa203cffd36b4e7f70cb}}<br />
* [https://www.postgresql.org/message-id/CAH2-Wzmj6pz98qZ6%2BRo-%3DtHvyBJ6q0yxHV8QLOr6O0mE20Nw9Q%40mail.gmail.com pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)]<br />
** Fixed in: {{PgCommitURL|d004147eb3ece6b5981dbdd3d918ffc3f23fc505}}<br />
* [https://www.postgresql.org/message-id/20181009.181536.142257785.horiguchi.kyotaro@lab.ntt.co.jp Bypass processing of wraparound autovacuums not marked as aggressive]<br />
** Problem exists since the point where aggressive vacuums have been introduced, v12 has only added extra logs to look after the impossible case of wraparound autovacuums not aggressive.<br />
** Fixed in: {{PgCommitURL|2aa6e331ead7f3ad080561495ad4bd3bc7cd8913}}<br />
* [https://www.postgresql.org/message-id/15733-7692379e310b80ec%40postgresql.org An insert destined at partition created after a column has been dropped from the parent table fails]<br />
** Fixed in: {{PgCommitURL|6b0208ebc436b33bd80ce264299b4b1b8d59b68a}}<br />
* [https://www.postgresql.org/message-id/7961.1552498252%40sss.pgh.pa.us RelationData.rd_partcheck should get its own memory context]<br />
** Fixed in: {{PgCommitURL|5f1433ac5e7f943b29ef01266b6b8fc915e6b917}}<br />
* [https://www.postgresql.org/message-id/15734-2daa8761eeed8e20@postgresql.org Walsender process crashing when executing SHOW ALL]<br />
** Fixed in: {{PgCommitURL|c34677fdaa73f089d557554a9cd479b9bd5b5143}}<br />
* [https://www.postgresql.org/message-id/016deb6b-1f0a-8e9f-1833-a8675b170aa9@postgresql.org Possible to store invalid SCRAM-SHA-256 Passwords]<br />
** Fixed in: {{PgCommitURL|ccae190b916f27fbe4079ee4664d34cd1be47b79}}<br />
* [https://www.postgresql.org/message-id/15781-2601b1002bad087c@postgresql.org BUG #15781: subselect on foreign table (postgres_fdw) can crash]<br />
** Fixed in: {{PgCommitURL|8cad5adb9c0be82e9f40d51b02a542439f47de9e}}<br />
* [https://www.postgresql.org/message-id/9813f079-f16b-61c8-9ab7-4363cab28d80@lab.ntt.co.jp selecting from partition directly can't use constraint exclusion]<br />
** Fixed in: {{PgCommitURL|e03ff739695cb731956763355e8e0f38c6905008}}<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Fixed in: {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
* [https://www.postgresql.org/message-id/FAD28A83-AC73-489E-A058-2681FA31D648@tvsquared.com Partition pruning is broken for stable WHERE conditions]<br />
** Fixed in: {{PgCommitURL|6630ccad7a25cad32e2d1a6833fb971602cb67fe}} and predecessor commits<br />
* [https://www.postgresql.org/message-id/flat/CAKcux6%3DuZEyWyLw0N7HtR9OBc-sWEFeByEZC7t-KDf15FKxVew%40mail.gmail.com Statistical aggregate functions are not working with partitionwise aggregate]<br />
** Fixed in: {{PgCommitURL|2657283256f1cab53d09d2c7db1ce9b7065193a0}}<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** Fixed in {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** Back-patched to v10; back-patching further is unattractive from both risk and work-required standpoints<br />
* [https://www.postgresql.org/message-id/20190618231233.GA27470@telsasoft.com Statistics with inheritance cause ANALYZE failures]<br />
** [https://www.postgresql.org/message-id/20190618235755.GA17759@telsasoft.com test case]<br />
** Fixed in {{PgCommitURL|14ef15a22246ca17c949e7a9d1abe14c8874d743}}<br />
* [https://www.postgresql.org/message-id/20190730211759.zqzt7xfchvmuja4i@development Change semantics of log_statement_sample_rate?]<br />
** Fixed in {{PgCommitURL|75506195da81d75597a4025b72f8367e6c45f60d}}<br />
* [https://www.postgresql.org/message-id/flat/CAK%3D1%3DWrek44Ese1V7LjKiQS-Nd-5LgLi_5_CskGbpggKEf3tKQ%40mail.gmail.com REL_12_STABLE crashing with assertion failure in ExtractReplicaIdentity]<br />
** The report mentions REL_12_STABLE, but it's a pre-existing issue just made visible by new checks. Nonetheless, it's not clear that there are real consequences beyond the assertion failure, so no change in prior branches.<br />
** Fixed in {{PgCommitURL|f63a5ead9d04467e1c1847bd5e3d87c4dca6cd35}}<br />
<br />
=== Nothing to do ===<br />
<br />
* [https://www.postgresql.org/message-id/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
** The consensus would be to increase the upper boundary of toast_tuple_target, but this means potentially breaking a category of dumps.<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoB_+PSoO4J2dKEgy9qKf2uNnbHHOOSUcz6f20f-=T-bdg@mail.gmail.com vacuumdb and new VACUUM options]<br />
== Resolved Issues ==<br />
<br />
=== resolved before 12rc1 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/TY2PR01MB2443EC8286995378AEB7D9F8F5B10%40TY2PR01MB2443.jpnprd01.prod.outlook.com ECPG DECLARE STATEMENT definitional and quality-of-implementation concerns]<br />
** Reverted by {{PgCommitURL|96b6c82c9dd4a6a91c7e54bf42d36da111959ec6}}<br />
* [https://www.postgresql.org/message-id/flat/48ee4c56-e1df-b39d-2cad-c7d80b120eb5%402ndquadrant.com ecpglib major version change]<br />
** Reverted by {{PgCommitURL|fbd1cb2fd9796a08a198d929774280ecce933057}}<br />
* [https://www.postgresql.org/message-id/31481.1568303470@sss.pgh.pa.us Leakproofness of texteq()/textne()]<br />
** Fixed in {{PgCommitURL|c160b8928c77cb52f52d7509465b6c7d8026bd27}}<br />
* [https://www.postgresql.org/message-id/22566.1568675619@sss.pgh.pa.us Nondeterministic collations break text_pattern_ops]<br />
** Fixed in {{PgCommitURL|2810396312664bdb941e549df7dfa75218d73a1c}}<br />
<br />
=== resolved before 12beta4 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAHU7rYZo_C4ULsAx_LAj8az9zqgrD8WDd4hTegDTMM1LMqrBsg@mail.gmail.com EvalPlanQual crash due to wrong slot tupdesc]<br />
** Commit {{PgCommitURL|ad0bda5d24ea2bcc72b5e50020e3c79bab10836b}} Author: Andres Freund<br />
** Fixed in {{PgCommitURL|27cc7cd2bc8a5e8efc8279bc5d2a8ae42fd8ad33}}<br />
* [https://www.postgresql.org/message-id/15977-f4eb49ebdcacc65b@postgresql.org BUG #15977: Inconsistent behavior in chained transactions]<br />
** behavior of AND CHAIN on implicit transactions is not consistent<br />
** Commit {{PgCommitURL|280a408b48d5ee42969f981bceb9e9426c3a344c}} Author: Peter Eisentraut<br />
** [https://commitfest.postgresql.org/24/2265/ fix ready], consisting in disabling chaining when in an implicit transaction<br />
** Fixed in {{PgCommitURL|862ef372d6b23629f93d4afc123ddd7d172501ac}}<br />
* [https://www.postgresql.org/message-id/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<br />
** Proposed patch is in thread [https://www.postgresql.org/message-id/4859321552643736@myt5-02b80404fd9e.qloud-c.yandex.net Change ereport level for QueuePartitionConstraintValidation]<br />
** Fixed in {{PgCommitURL|db438318997b75f4b40c61258da56384039fa43f}}<br />
* [https://postgr.es/m/20190816200048.GA5514@alvherre.pgsql Images in documentation don't work in VPATH]<br />
** Fixed in {{PgCommitURL|842ac79407a136}}<br />
* [https://www.postgresql.org/message-id/d6ffbebb-a0d2-181c-811d-b029b2225ed7@iki.fi default_table_access_method is not in sample config file]<br />
** {{PgCommitURL|f7db0ac7d5b6ba9728616a1cc36288cb4f817e66}}<br />
* [https://www.postgresql.org/message-id/aed6cc9f-98f3-2693-ac81-52bb0052307e%402ndquadrant.com postgresql.auto.conf file with duplicate entries not handled properly]<br />
** Code fix committed at {{PgCommitURL|f1bf619acdff15b88b5729f8de6df4eed609b3a0}}<br />
** Doc fix committed at {{PgCommitURL|45aaaa42fefad6e2f164647e373346a5a4123dad}}<br />
<br />
=== resolved before 12beta3 ===<br />
<br />
* [https://postgr.es/m/CAPpHfdvGVegF_TKKRiBrSmatJL2dR9uwFCuR%2BteQ_8tEXU8mxg%40mail.gmail.com Hash join explain can fail with "bogus varno: 65000"]<br />
** Commit {{PgCommitURL|5f32b29c18195299e90c1fb6c8945e9a46d772d2}} Author: Andres Freund<br />
** Fixed in: {{PgCommitURL|2abd7ae9b20bcd810d4f19d28aefb97048813825}}<br />
* [https://www.postgresql.org/message-id/CAE9k0PmNaMD2oHTEAhRyxnxpaDaYkuBYkLa1dpOpn=RS0iS2AQ@mail.gmail.com Wrong-slot-type assertion failure]<br />
** Commit {{PgCommitURL|15d8f83128e15de97de61430d0b9569f5ebecc26}} Author: Andres Freund<br />
** Fixed in: {{PgCommitURL|af3deff3f2ac79585481181cb198b04c67486c09}}<br />
* [https://www.postgresql.org/message-id/73436355-6432-49B1-92ED-1FE4F7E7E100@finefun.com.au virtual tuple table slot does not have system attributes]<br />
** Commit {{PgCommitURL|277cb789836b5ddf81aabb80c2058268c70e2f36}} Author: Andres Freund<br />
** Fixed in: {{PgCommitURL|ecbdd009344d3a00733e4382f50137b5e0248ce8}}<br />
* [https://www.postgresql.org/message-id/CAH2-WznCNvhZpxa__GqAa1fgQ9uYdVc=_apArkW2nc-K3O7_NA@mail.gmail.com Adversarial/pathological case for new nbtree split point choice logic]<br />
** Commit {{PgCommitURL|fab2502433870d98271ba8751f3794e2ed44140a}} Author: Peter Geoghegan<br />
** Fixed in: {{PgCommitURL|e3899ffd8beafdaaa037b503163a9f572e9fc729}}<br />
* [https://www.postgresql.org/message-id/CAD21AoCqs8iN04RX=i1KtLSaX5RrTEM04b7NHYps4+rqtpWNEg@mail.gmail.com Add vacuum_index_cleanup for toast relations?]<br />
** Commit: {{PgCommitURL|a96c41feec6b6616eb9d5baee9a9e08c20533c38}}, Author: Masahiko Sawada, Owner: Robert Haas<br />
** Fixed in: {{PgCommitURL|ce59b75d449d9152667ce3e9eab33ef2872bfd98}}<br />
* [https://www.postgresql.org/message-id/20190611061115.njjwkagvxp4qujhp%40alap3.anarazel.de check_recovery_target_lsn() does a PG_CATCH without a throw]<br />
** Commit {{PgCommitURL|2dedf4d9a899b36d1a8ed29be5efbd1b31a8fe85}} Author: Peter Eisentraut<br />
** Fixed in: {{PgCommitURL|21f428ebde39339487c271a830fed135d6032d73}}<br />
* [https://www.postgresql.org/message-id/7586.1560540361@sss.pgh.pa.us psql error messages are now too verbose]<br />
** Commit {{PgCommitURL|cc8d41511721d25d557fc02a46c053c0a602fed0}} Author: Peter Eisentraut<br />
** Fixed in: {{PgCommitURL|3f3542621f131379e32e9283d40853cb6d03a97f}}<br />
* [https://www.postgresql.org/message-id/20190607165105.vn4bl6piofroj3um@alap3.anarazel.de BulkInsertStates and copy.c with partitioned tables]<br />
** Fixed in: {{PgCommitURL|b8ef33b2d14519da0d038e9d63f51a6714ef764a}}<br />
* [https://www.postgresql.org/message-id/8736jdhbhc.fsf@ansel.ydns.eu Crash in mcv_get_match_bitmap with sqlsmith]<br />
** Fixed in: {{PgCommitURL|e8b6ae2130e3a95bb776708a9a7c9cb21fe8ac87}}<br />
* [https://www.postgresql.org/message-id/68d00017-ae5c-b14f-fc3a-c9e38e3ce792%40iki.fi GiST Page can become unrecyclable due to PageDeleteXid wraparound]<br />
** Commit {{PgCommitURL|7df159a620b760e289f1795b13542ed1b3e13b87}} Author: Heikki Linnakangas<br />
** Fixed in: {{PgCommitURL|6655a7299d835dea9e8e0ba69cc5284611b96f29}}<br />
* [https://www.postgresql.org/message-id/CA+u7OA5Hp0ra235F3czPom_FyAd-3+XwSJmX95r1+sRPOJc9VQ@mail.gmail.com REINDEX CONCURRENTLY causes ALTER TABLE to fail]<br />
** Fixed in: {{PgCommitURL|28bbf7a81b3a30504cc7dfdbd76b410d1f127b8e}}<br />
* [https://www.postgresql.org/message-id/20190801184333.GA21369@alvherre.pgsql Progress reporting of REINDEX, CREATE TABLE and CLUSTER ignore each other]<br />
** A progress may be started while another one is already in progress. Hence, if progress gets stopped the previously-started state is removed, causing all follow-up updates to not happen.<br />
** Progress updates happening in a code path shared between those three commands may clobber a previous state present. <br />
** Fixed in: {{PgCommitURL|da47e43dc32e3c5916396f0cbcfa974b371e4875}}<br />
<br />
=== resolved before 12beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/CAGPqQf0cYjm1%3Drjxk_6gU0SjUS70%3DyFUAdCJLwWzh9bhNJnyVg%40mail.gmail.com CREATE TABLE .. PARTITION OF doesn't respect default_tablespace]<br />
** Fixed in: {{PgCommitURL|a36c84c3e4a9bee6baa7}}<br />
* [https://www.postgresql.org/message-id/CALAY4q99FcFCoG6ddke0V-AksGe82L_+bhDWgEfgZBakB840zA@mail.gmail.com with oids option not removed in pg_dumpall]<br />
** Commit {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}<br />
** Fixed in: {{PgCommitURL|657c2384c6c79c6ed0d6f71f811b2fc7c41f104a}}<br />
* [https://www.postgresql.org/message-id/20190522083038.GA16837@paquier.xyz pg_dump throwing "column number -1 is out of range 0..36" on HEAD]<br />
** Fixed in: {{PgCommitURL|54487d1560619a0027e0651d1b8d715ca8fc388c}}<br />
* [https://www.postgresql.org/message-id/CA%2BrenyUuSmYgmZjKc_DfUNVZ0uttF91-FwhDVW3F7WEPj0jL5w%40mail.gmail.com ddl.sgml still says foreign keys can't point to partitioned tables]<br />
** Commit {{PgCommitURL|f56f8f8da6afd8523b4d5284e02a20ed2b33ef8d}} Author: Alvaro Herrera<br />
** Fixed in: {{PgCommitURL|f73293aba4d43e48707e361b2b1ef1465fef46e0}}<br />
* [https://www.postgresql.org/message-id/20190601191007.GC1905@paquier.xyz psql completion bugs with access methods]<br />
** Fixed in: {{PgCommitURL|0240a00fbd4fd14f577edf8d36a032237fd0b9cb}}<br />
* [https://www.postgresql.org/message-id/15832-b1bf336a4ee246b5@postgresql.org COPY into a partitioned table breaks its indexes]<br />
** Fixed in: {{PgCommitURL|56b3b3838284f53c83556592e60688522155f57f}}<br />
* [https://www.postgresql.org/message-id/20190607043415.GE1736@paquier.xyz be-gssapi-common.h not in correct location]<br />
** Fixed in: {{PgCommitURL|35b2d4bc0eb5d61a2a294ccb6b2e4abdad307604}}<br />
* [https://www.postgresql.org/message-id/CAJrrPGcAxsMM7n__HJRPBrh7Y6ruU6LetfPD=cPGeW=G49na0g@mail.gmail.com pg_basebackup failure after setting default_table_access_method option]<br />
** Fixed in: {{PgCommitURL|fff2a7d7bd09db38e1bafc1303c29b10a9805dc0}}<br />
* [https://www.postgresql.org/message-id/CALfoeiugyrXZfX7n0ORCa4L-m834dzmaE8eFdbNR6PMpetU4Ww%40mail.gmail.com Inconsistency between table am callback and table function names]<br />
** many commits, Author: Andres Freund<br />
** Fixed in: {{PgCommitURL|73b8c3bd2889fed986044e15aefd0911f96ccdd3}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f-2rx+E9mG3xrCVHupefMjAp1+tpczQa9SEOZWyU7fjEA@mail.gmail.com Documents don't warn about using too many partitions]<br />
** Fixed in: {{PgCommitURL|e788e849addd56007a0e75f3b5514f294a0f3bca}}<br />
* [https://www.postgresql.org/message-id/CAEZATCUhT9rt7Ui%3DVdx4N%3D%3DVV5XOK5dsXfnGgVOz_JhAicB%3DZA%40mail.gmail.com Multivariate MCV stats can leak data to unprivileged users]<br />
** Fixed by {{PgCommitURL|6cbfb784c3c91146148a76d50cda6f69ae6a79fb}} et seq<br />
* [https://www.postgresql.org/message-id/20190527203713.GA58392@gust.leadboat.com \connect uses the same IP as the existing connection, docs no longer match behavior, etc.]<br />
** Commit {{PgCommitURL|6e5f8d4}} Author: Fabien Coelho<br />
** Fixed by {{PgCommitURL|313f56ce2d1b9dfd3483e4f39611baa27852835a}}<br />
<br />
=== resolved before 12beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/20190225074539.az6j3u464cvsoxh6@depesz.com Segfault when restoring -Fd dump on current HEAD]<br />
** Fixed in {{PgCommitURL|7fcdb5e0021}}<br />
* [https://www.postgresql.org/message-id/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com pg_dump is broken for partition tablespaces]<br />
** Fixed in commits: {{PgCommitURL|87259588d0ab0b8e742e30596afa7ae25caadb18}}<br />
** and {{PgCommitURL|3b23552ad8bb}}<br />
* [https://www.postgresql.org/message-id/15727-0be246e7d852d229@postgresql.org PANIC: cannot abort transaction XXX, it was already committed]<br />
** One issue fixed in: {{PgCommitURL|41f5e04aec6cf63ba8392adf70e9289e9c3706d6}}<br />
** Another issue fixed in: {{PgCommitURL|f7feb020c3d8d5aff24204af28359b99ee65bf8f}}<br />
* [https://www.postgresql.org/message-id/201902021315.6h6ktmmsgjmx@alvherre.pgsql remove \cset from pgbench]<br />
** Fixed in: {{PgCommitURL|25ee70511ec2ccbef0ad3fe64875a4d552cdcd50}}<br />
* [https://www.postgresql.org/message-id/20190322032612.GA323@alvherre.pgsql pg_partition_root crashes when using top-most parent in input]<br />
** Fixed in: {{PgCommitURL|2ab6d28d233af17987ea323e3235b2bda89b4f2e}}<br />
* [https://www.postgresql.org/message-id/CA+HiwqEGoa485g18mt9GUdF8fH4mKDgpeoc32XiW-dRUFpN5Lw@mail.gmail.com Server crash in transformPartitionRangeBounds]<br />
** Fixed in: {{PgCommitURL|cdde886d36b5a4d7ad9e1d02596f7fa1c8c129e3}}<br />
* [https://www.postgresql.org/message-id/20190326020853.GM2558@paquier.xyz Misleading errors with column references in default expressions and partition bounds]<br />
** Fixed in: {{PgCommitURL|ecfed4a12247cf4659eee6b6ea27405e35fe57f8}}<br />
* [https://www.postgresql.org/message-id/8305.1553884377@sss.pgh.pa.us Planner's partitionwise-join code crashes under GEQO]<br />
** Fixed in: {{PgCommitURL|7ad6498fd5a654de6e743814c36cf619a3b5ddb6}}<br />
* [https://www.postgresql.org/message-id/flat/19465.1541636036@sss.pgh.pa.us Inadequate index locking causes Assert failure]<br />
** Fixed in: {{PgCommitURL|9c703c169a872d144f2f79d2fb211c82587adfa7}}<br />
* [https://www.postgresql.org/message-id/87wolmg60q.fsf@news-spur.riddles.org.uk Inlining of nested CTEs with recursive terms]<br />
** Fixed in: {{PgCommitURL|9476131278c7bfc435ad9a21fc8e981272ac0dd2}}<br />
* [https://www.postgresql.org/message-id/DF4PR8401MB11964EDB77C860078C343BEBEE5A0@DF4PR8401MB1196.NAMPRD84.PROD.OUTLOOK.COM Indexes part of a partition tree cannot be run with REINDEX CONCURRENTLY]<br />
** Fixed in: {{PgCommitURL|ef6f30fe77af69a8c775cca82bf993b10c9889ee}}<br />
* [https://www.postgresql.org/message-id/flat/CABUevEzD_duH_hGyZw14o%2BkhHBw-rWSSAxbEKt5HWy2cK0Djdw%40mail.gmail.com#d8a9d175134a072dd1477c3fac96f76a Keep track of checksum failures in shared object, last failure time and pg_stat_checkums view]<br />
** Commit: {{PgCommitURL|6b9e875f7286d8535bff7955e5aa3602e188e436}}, Author: Magnus Hagander, Owner: Magnus Hagander<br />
** Fixed in: {{PgCommitURL|77bd49adba4711b4497e7e39a5ec3a9812cbd52a}}<br />
* [https://www.postgresql.org/message-id/5CAF3B8F.2090905@lab.ntt.co.jp Partition tuple routing code does not always call EndForeignInsert]<br />
** Commit: {{PgCommitURL|3f2393edefa5ef2b6970a5a2fa2c7e9c55cc10cf}}, Author: David Rowley, Amit Langote and Álvaro Herrera: Owner: Álvaro Herrera<br />
** Fixed in: {{PgCommitURL|3a45321a491711b556d2cf8f6904ab989b9d0b08}}<br />
* [https://www.postgresql.org/message-id/a620f85a-42ab-e0f3-3337-b04b97e2e2f5%40redhat.com COLLATE: Hash partition vs UPDATE]<br />
** Fixed in: {{PgCommitURL|4b40e44f07c727c7a82b291d3b60098dd99f3f64}}<br />
* [https://www.postgresql.org/message-id/20190411134947.GA22043@alvherre.pgsql Consider invalid indexes for REINDEX INDEX CONCURRENTLY?]<br />
** Fixed in: {{PgCommitURL|a6dcf9df4d91ff0db23579f9114079abe6f3e2bf}}<br />
* [https://www.postgresql.org/message-id/366.1555382816@sss.pgh.pa.us ExecForceStoreMinimalTuple leaks memory like there's no tomorrow]<br />
** Commit: {{PgCommitURL|4da597edf1bae0cf0453b5ed6fc4347b6334dfe1}}, Author: Andres Freund, Ashutosh Bapat, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|88e6ad3054ddd5aa0dee12e5def2c335fe92a414}}<br />
* [https://www.postgresql.org/message-id/CAOuzzgqS-CL18_zKF7pF-wymG8mUeUZveNYYSrXKQRn1VaJsug@mail.gmail.com GSSAPI encryption missing protocol documentation]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/8416d227-6e9d-092a-4475-b453e1d7d433@2ndquadrant.com New regression tests for GSSAPI encryption are unstable]<br />
** Commit: {{PgCommitURL|b0b39f72b9904bcb80f97b35837ccff1578aa4b8}}, Author: Robbie Harwood, Owner: Stephen Frost<br />
** Fixed in {{PgCommitURL|eb882a1b717589777e068dc6671830226f3aa7f0}}<br />
* [https://www.postgresql.org/message-id/flat/20190330224333.GQ5815%40telsasoft.com clean up docs for v12]<br />
** Fixed in {{PgCommitURL|148266fa354a47543f6c0325cd1ea900ead4aac6}}<br />
* [https://www.postgresql.org/message-id/CAH2-Wzm08nr+JPx4jMOa9CGqxWYDQ-_D4wtPBiKghXAUiUy-nQ@mail.gmail.com Pathological performance when inserting NULL values into unique index]<br />
** Commit: {{PgCommitURL|dd299df8189bd00fbe54b72c64f43b6af2ffeccd}}, Author: Peter Geoghegan, Owner: Peter Geoghegan<br />
** Fixed in {{PgCommitURL|9b10926263d831fac5758f1493c929a49b55669b}}<br />
* [https://www.postgresql.org/message-id/20190408002847.GA904@telsasoft.com Cleanup/remove/update references to OID column]<br />
** Commit: {{PgCommitURL|578b229718e8f15fa779e20f086c4b6bb3776106}}, Author: Andres Freund, Owner: Andres Freund<br />
** Fixed in {{PgCommitURL|f6b39171f3d65155b9390c2c69bc5b3469f923a8}}<br />
* [https://www.postgresql.org/message-id/15751.1555256860@sss.pgh.pa.us topminnow triggered assertion failure with vacuum_index_cleanup]<br />
** Fixed in {{PgCommitURL|dd69597988859c51131e0cbff3e30432db4259e1}}<br />
* [https://www.postgresql.org/message-id/CAMkU=1x8taZfsbPkv_MsWbTtzibW_yQHXoMhF_DTtm=z2hVHDg@mail.gmail.com compiler warning in pgcrypto imath.c]<br />
** Commit: {{PgCommitURL|48e24ba6b7fd3bfd156b51e8d768fd48df0d288b}}, Author: Noah Misch, Owner: Noah Misch<br />
** Fixed in {{PgCommitURL|726cc4242a2f766c8280a72ef7c8418965d139c8}}<br />
* [https://www.postgresql.org/message-id/CAHGQGwHa_dX%3DdRcbR5QVTs6W5mgCy3qZ2fEwREaiXpES1B2%2Bjw%40mail.gmail.com Add TRUNCATE option to vacuum command as well as reloption]<br />
** Commit: {{PgCommitURL|119dcfad988d5b5d9f52b256087869997670aa36}}, Author: Tsunakawa Takayuki, Owner: Fujii Masao<br />
** Fixed in {{PgCommitURL|b84dbc8eb80b43e554891c459a19969d9fbdefe5}}<br />
* [https://www.postgresql.org/message-id/20190416180452.3pm6uegx54iitbt5@alap3.anarazel.de Improvements in no-fsm-for-small-rels patch suggested by Andres Freund]<br />
** Commit: {{PgCommitURL|b0eaa4c51bbff3e3c600b11e5d104d6feb9ca77f}}, Author: John Naylor, Amit Kapila, Owner: Amit Kapila<br />
** Fixed in {{PgCommitURL|7db0cde6b58eef2ba0c70437324cbc7622230320}}<br />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
** Fixed in {{PgCommitURL|47a338cfcd67139a1f91892b080934fcfc3aea03}}<br />
* [https://www.postgresql.org/message-id/20190430151735.wi52sxjvxsjvaxxt@alap3.anarazel.de Heap lock levels for REINDEX INDEX CONCURRENTLY not quite right?]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|add85ead4ab969c1e31d64f4476c2335856f4aa9}}<br />
* [https://www.postgresql.org/message-id/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<br />
** Fixed in {{PgCommitURL|508300e2e141a9fd87758ce01374c5b0597986fd}}<br />
* [https://www.postgresql.org/message-id/CA+hUKGJRzLo7tZExWfSbwM3XuK7aAK7FhdBV0FLkbUG+W0v0zg@mail.gmail.com Wrong answers from queries using a GIST index]<br />
** Commit: {{PgCommitURL|9155580fd5fc2a0cbb23376dfca7cd21f59c2c7b}}, Author: Anastasia Lubennikova, Andrey V. Lepikhov, Owner: Heikki Linnakangas<br />
** Fixed in {{PgCommitURL|22251686f07f70527aecda22ab5402986884f6f5}}<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com Circular dependency between libpgcommon and libpgfeutils]<br />
** Fixed in {{PgCommitURL|fc9a62af3f87f4bec1e8c904ea99ae50f3c881ef}}<br />
* [https://www.postgresql.org/message-id/CA%2BTgmoZP-CTmEPZdmqEOb%2B6t_Tts2nuF7eoqxxvXEHaUoBDmsw%40mail.gmail.com Should effective_io_concurrency + 10 be used for an index's page deletion table scans, or a new GUC]<br />
** Decision: leave the "+ 10" in for v12, and revisit in a later release when we have a better idea what kind of GUCs we want to control prefetching here and elsewhere<br />
* [https://www.postgresql.org/message-id/CAE9k0P=FvcDswnSVtRpSyZMpcAWC=Gp=ifZ0HdfPaRQ=__LBtw@mail.gmail.com Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()]<br />
** Commit {{PgCommitURL|86b85044e823a304d2a265abc030254d39efe7df}} Author: David Rowley, Andres Freund<br />
** Decision: it's ok to have the unused parameter<br />
* [https://www.postgresql.org/message-id/15804-3721117bf40fb654@postgresql.org Assertion failure when using logging_collector on Windows]<br />
** Commit {{PgCommitURL|57431a911d3a650451d198846ad3194900666152}} Author: Peter Eisentraut<br />
** Fixed for 12beta1 by reverting, in {{PgCommitURL|833451552925d0175e1e15128e411ddef9a36996}}, the necessary changes are too big for v12<br />
<br />
== Won't Fix ==<br />
<br />
* [https://www.postgresql.org/message-id/10797.1552679128@sss.pgh.pa.us Memory leak associated with dubious RelationData.rd_pdcxt handling]<br />
** Commit: {{PgCommitURL|898e5e3290a72d288923260143930fb32036c00c}}, Author: Robert Haas, Owner: Robert Haas<br />
** A proposed patch exists, but some feel that cure is worse than the disease, so we may end up doing nothing for v12<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: June 20, 2019<br />
* beta3: Aug. 8, 2019<br />
* beta4: Sep. 12, 2019<br />
* rc1: Sep. 26, 2019<br />
* GA: Oct. 3, 2019<br />
<br />
[[Category:Open_Items]]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PgCon_2019_Developer_Meeting&diff=33421PgCon 2019 Developer Meeting2019-05-07T13:47:18Z<p>Dsteele: /* RSVPs */</p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Tuesday 28 May, 2019 at the University of Ottawa, prior to pgCon 2019. In order to keep the numbers manageable, this meeting is by '''invitation only'''.<br />
<br />
The invitation list for the meeting has changed this year to include representatives from various project sub-teams, for example, packagers, the release team, Code of Conduct committee and more.<br />
<br />
As at last years event, an Unconference will be held on Wednesday for in-depth discussion of technical topics.<br />
<br />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Define the schedule for the 13.0 release cycle<br />
* Address any proposed timing, policy, or procedure issues<br />
* Receive updates from project sub-teams on their activities and discuss any resulting issues or concerns.<br />
* Address any proposed [http://en.wikipedia.org/wiki/Wicked_problem Wicked problems]<br />
<br />
== Time & Location ==<br />
<br />
The meeting will be:<br />
<br />
* 9:00AM to 12PM<br />
* DMS TBC<br />
* University of Ottawa.<br />
<br />
Coffee, tea and snacks will be served starting at 8:45am. Lunch will be after the meeting.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname). Note that we can accommodate a '''maximum of 30'''!<br />
<br />
# Joe Conway<br />
# Jeff Davis<br />
# Andrew Dunstan<br />
# Peter Eisentraut<br />
# Andres Freund<br />
# Stephen Frost<br />
# Peter Geoghegan<br />
# Devrim Gündüz<br />
# Robert Haas<br />
# Magnus Hagander<br />
# Stacey Haysler (present for CoC report and discussion only)<br />
# Álvaro Herrera<br />
# Amit Kapila<br />
# Jonathan Katz<br />
# Alexander Korotkov<br />
# Tom Lane<br />
# Heikki Linnakangas<br />
# Noah Misch<br />
# Bruce Momjian<br />
# Thomas Munro<br />
# John Naylor<br />
# Dave Page<br />
# Michael Paquier<br />
# David Rowley<br />
# Masahiko Sawada<br />
# David Steele<br />
# Robert Treat<br />
# Tomas Vondra<br />
<br />
The following people will not be in Ottawa, and do not plan to attend:<br />
<br />
* Christoph Berg<br />
* Vik Fearing<br />
* Andreas Scherbaum<br />
* Sarah Conway Schnurr<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
<br />
== Agenda Items ==<br />
<br />
* 13.0 release and commitfest schedule (Dave)<br />
* Contributor Recognition (Andres, happy to share / pass, but should be discussed)<br />
** [https://www.postgresql.org/community/contributors/ contributors] page update - how well is it working?<br />
** should the developer meeting serve as recognition? <br />
* The Evolving Developer Meeting: Goals & What We Want to Accomplish by the end of it? (Jonathan, happy to share)<br />
* SQL standard update (Peter E.)<br />
* ''Please add suggestions for agenda items here. (with your name)''<br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:10<br />
|Welcome and introductions<br />
|Dave Page<br />
<br />
|-<br />
|09:10 - 09:30<br />
|Code of Conduct report and discussion<br />
|Stacey Haysler<br />
<br />
|- <br />
|09:30 - 09:45<br />
|12.0 release and commitfest schedule<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:30 - 11:00<br />
|Coffee break<br />
|All<br />
<br />
|- <br />
|11:00 - 11:15<br />
|Improving packaging processes<br />
|Devrim Gündüz<br />
<br />
|- <br />
|11:50 - 12:00<br />
|Any other business<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:00<br />
|Lunch<br />
|<br />
<br />
|}<br />
<br />
Note: This timetable is a rough guide only. Items will start as soon as the previous discussion is complete (breaks will not move however). Any remaining time before lunch may be used for Commitfest item triage or other activities.</div>Dsteelehttps://wiki.postgresql.org/index.php?title=GCI_2018&diff=32546GCI 20182018-09-17T14:56:58Z<p>Dsteele: /* Help ESL Students with Job Applications */</p>
<hr />
<div>This page is for listing tasks and collecting ideas for the yearly Google Code-in contests. <br />
<br />
https://codein.withgoogle.com/<br />
<br />
https://developers.google.com/open-source/gci/how-it-works<br />
<br />
== Regarding Project Ideas ==<br />
<br />
Project ideas are to be added here by community members.<br />
<br />
'''NOTE:''' Google looks for the following for each task:<br />
<br />
* A mix of tasks across multiple categories. (Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface)<br />
* Tasks of appropriate scope, length, and complexity.<br />
* Fully fleshed out descriptions with enough information to get started on.<br />
* Clear and understandable descriptions and titles.<br />
* Appropriate tags for searchability.<br />
<br />
Please add new sections following this format.<br />
<br />
== Mentors (2018) ==<br />
<br />
The following individuals have been listed as possible mentors on the below projects, and/or offered to be mentors for student-proposed projects:<br />
<br />
* Renee Phillips<br />
* Corey Huinker<br />
* Lætitia Avrot<br />
* Stephen Frost<br />
* Sarah Conway<br />
* Vik Fearing<br />
* Evan Macbeth<br />
* Keith Fiske<br />
<br />
==Give a Local Presentation==<br />
<br />
=====Task Description=====<br />
<br />
PostgreSQL is a rapidly growing open source database, but one area that needs improvement is reaching outside of the internal community to the external open-source world to educate others about PostgreSQL and help them get started. Because of that, we can use your help to present a talk focused on PostgreSQL to an audience of your choosing. Examples would include local technology groups, technology user groups, a school, or clubs in your area. Some potential audiences can be found through Meetup: http://meetup.com/. The length of the talk can vary from a 5 minute lightning talk to a 30-60 minute long presentation or tutorial. <br />
<br />
The expected work to be uploaded will be a PDF version of the slides used during the presentation.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Research<br />
* Presentation<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Outreach/Research<br />
<br />
==Create an Educational Video==<br />
<br />
=====Task Description=====<br />
<br />
More online resources are always helpful for those learning PostgreSQL. Create a video demonstration illustrating a topic of your choosing in PostgreSQL; some examples would include a beginners introduction and history of PostgreSQL, how to get started in PostgreSQL, how to perform load balancing and high availability in a PostgreSQL cluster, how to run PostgreSQL within a Kubernetes or OpenShift environment, different monitoring statistics for your cluster, and so on.<br />
<br />
The video should be between 5-15 minutes, and must be your original work. <br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Video<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Developing a Lesson Plan==<br />
<br />
=====Task Description=====<br />
<br />
A major priority of the PostgreSQL organization is to expand awareness and education of PostgreSQL throughout the world, in a diverse and inclusive manner. One of our goals is to educate all groups, ranging from middle school, high school, and college students to adults from all ages and backgrounds, of open source technology and PostgreSQL.<br />
<br />
The expected outcome of this task is to draft sample training materials and a lesson plan for a younger age group (ranging from kids to teenagers) on getting started with PostgreSQL. It should be fun and engaging, with interactive tasks for hands-on learning. This can be submitted in any format, ranging from slides to a document-based format. The lesson plan should be prefaced with the intended audience, the difficulty level, and the estimated amount of time to complete the training. <br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Research<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Outreach/Research<br />
<br />
==Design a Logo for a Conference==<br />
<br />
=====Task Description=====<br />
<br />
PostgreSQL has several conferences that revolve around educating and discussing PostgreSQL within the community. One of these conferences, Postgres Open SV 2019, is in need of a new, updated, and high-resolution logo for next year's conference. The website from 2018 with the currently existing logo can be found here:<br />
<br />
https://2018.postgresopen.org/<br />
<br />
The requirements are as follows:<br />
<br />
1) Submissions should be high-resolution (PNG or SVG) and should include a source file.<br />
<br />
2) The logo should resonate well with the current website design, as next year's design will be similar to the existing.<br />
<br />
3) While it does not need to resemble the current logo, it does need to center around an elephant as the theme. The reasoning for this is the official logo for PostgreSQL itself is an elephant: https://www.postgresql.org/media/img/about/press/elephant.png<br />
<br />
4) Provide a brief summary of your logic behind the design of the logo and your approach.<br />
<br />
=====Tags=====<br />
<br />
* User Interface<br />
* Graphics<br />
* Design<br />
* Logo<br />
<br />
=====Categories=====<br />
<br />
User Interface<br />
<br />
==Reviewing Patches==<br />
<br />
=====Task Description=====<br />
<br />
PostgreSQL development revolves around [[CommitFest]] periods where any and all volunteers are needed to assist in reviewing proposed patches. Your task would be to select an open patch, evaluate it, and ensure it does what the author intends. <br />
<br />
Please demonstrate your testing process and include screenshots of the steps taken, along with the proof that it is working, in a document that will be submitted for evaluation as proof of completing the task.<br />
<br />
More information can be found here:<br />
<br />
https://wiki.postgresql.org/wiki/Reviewing_a_Patch<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* SQL<br />
* Databases<br />
* C<br />
* C-language<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
==Improve PostgreSQL Regression Test Coverage==<br />
<br />
=====Task Description=====<br />
<br />
PostgreSQL can use additional development in the area of regression tests. Regression testing ensures that within PostgreSQL, new changes and additions aren't breaking existing functionality. Your task will be to introduce new regression tests for command line utilities and extensions that are poorly covered, as shown on https://coverage.postgresql.org/. <br />
<br />
The current regression test coverage for PostgreSQL isn't great, to the point where some areas of the code are covered only at single-digit-percent levels.<br />
<br />
Having good regression tests for such an important project as PostgreSQL is really key to minimizing the chance that any regressions are introduced. PostgreSQL's build system includes a "make coverage-html" to generate the report.<br />
<br />
Please note that this project involves writing SQL code and Perl code, at a minimum, to implement the tests necessary to increase the code coverage of the PostgreSQL regression tests.<br />
<br />
More information can be found in the [https://www.postgresql.org/docs/10/static/regress.html official documentation] on regression tasks.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* SQL<br />
* Perl<br />
* Databases<br />
* C<br />
* C-language<br />
* Development<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
==pgAdmin 4 Bug - Setting up SMTP with Docker==<br />
<br />
=====Task Description=====<br />
<br />
There is no currently existing documentation for setting up SMTP when running the official Docker image for pgAdmin 4. Without SMTP, users cannot change their password or use the "forgot password" option. The expected outcome from this task would be to determine how to configure SMTP with the Docker container and write up documentation illustrating the steps. <br />
<br />
A requirement would be to create a PostgreSQL community account. The resulting documentation would be sent in to the pgadmin4-hackers mailing list for review, and uploaded as a file for proof of completion. https://www.postgresql.org/list/pgadmin-hackers/<br />
<br />
The original bug report can be found here: https://redmine.postgresql.org/issues/3599<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* SQL<br />
* Databases<br />
* Development<br />
* Documentation<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
Documentation / Training<br />
<br />
==PostGIS Bug - Windows Installer==<br />
<br />
=====Task Description=====<br />
<br />
When installing PostGIS on Microsoft Windows, the installer shows a "Database Connection Information" dialog to supply User Name, Password, and Port. The installer will begin to install PostGIS, however, if there is a mistake in the connection information, the installer fails part-way in, requiring it to be run again from the beginning.<br />
<br />
It would be nice to allow multiple attempts to correct the connection information, if say, there was a typo with the password. This way the installer only needs to be run once (for example, using Application Stack Builder, which downloads the installer to %TEMP%).<br />
<br />
Not only should the connection info establish a connection to a database, but select count(*)=1 from pg_user where usename=$1 and usecreatedb;. If there is an error, the user should be able to go back and correct, try again, repeat or cancel. Correct connection info should be established before starting the install process.<br />
<br />
A requirement would be to create a PostgreSQL community account. The resulting documentation would be sent in to the postgis-devel mailing list for review, and uploaded as a file for proof of completion. https://lists.osgeo.org/mailman/listinfo/postgis-devel<br />
<br />
The original bug report can be found here: https://trac.osgeo.org/postgis/ticket/516<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* Authentication<br />
* SQL<br />
* Databases<br />
* Development<br />
* Documentation<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
Documentation / Training<br />
<br />
==Participate in Mailing Lists==<br />
<br />
=====Task Description=====<br />
<br />
The purpose of this task is to introduce you to community involvement and participation. The first required step will be to [https://www.postgresql.org/account/signup/ create a community account] if you do not already have one and subscribe to the [https://www.postgresql.org/list/ pgsql-bugs mailing list]. <br />
<br />
Secondly, you will need to participate in a mailing list thread when a user reports a bug through reproducing their reported bug and responding to the community thread confirming the existence of the bug. Include the operating system and version of PostgreSQL you are running, in addition to the steps taken to reproduce the original issue. <br />
<br />
The expected submission for this task will be a link to the mailing list archive for the relevant thread and a screenshot of the reproduced problem on your machine, showing the problem reported by the original user.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* Quality Assurance<br />
* SQL<br />
* Databases<br />
* Development<br />
* Testing<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
User Interface<br />
<br />
==PostgreSQL US - Develop an Integrated Form==<br />
<br />
=====Task Description=====<br />
<br />
The United States PostgreSQL Association, affectionately known as PgUS, is a IRS 501(c)(3) non-profit public charity that has the intention of supporting the growth and education of PostgreSQL, The World's Most Advanced Open Source Database, throughout the United States. <br />
<br />
Your task will be to fork the [https://github.com/pg-us/pgusweb official repository] hosting the PostgreSQL US website and propose a patch / pull request that integrates the currently existing Diversity Scholarship form hosted [https://docs.google.com/forms/d/1dgFUVXHgJ0sLAETJaAciLFetvFq5_S0-juZ3g8QyeVc/edit?ts=58f14198 on Google Forms] into a web page of its own.<br />
<br />
A further description of the Diversity Scholarship and its purpose can be found [https://postgresql.us/diversity/ here].<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Design<br />
* User Interface<br />
* HTML<br />
* CSS<br />
* Bootstrap<br />
<br />
=====Categories=====<br />
<br />
Code<br />
<br />
User Interface<br />
<br />
==PostgreSQL US - Develop a Resolution Tracker==<br />
<br />
=====Task Description=====<br />
<br />
The United States PostgreSQL Association, affectionately known as PgUS, is a IRS 501(c)(3) non-profit public charity that has the intention of supporting the growth and education of PostgreSQL, The World's Most Advanced Open Source Database, throughout the United States. <br />
<br />
Your task will be to fork the [https://github.com/pg-us/pgusweb official repository] hosting the [https://postgresql.us/ PostgreSQL US website] and propose a patch / pull request that contains a form in which board members can record resolutions in addition to information relating to who voted on the resolution, what the resolution is along with a description, and what the resulting votes are.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Design<br />
* User Interface<br />
* HTML<br />
* CSS<br />
* Bootstrap<br />
<br />
=====Categories=====<br />
<br />
Code<br />
<br />
User Interface<br />
<br />
==PostgreSQL US - Draft a new Website Design==<br />
<br />
=====Task Description=====<br />
<br />
The United States PostgreSQL Association, affectionately known as PgUS, is a IRS 501(c)(3) non-profit public charity that has the intention of supporting the growth and education of PostgreSQL, The World's Most Advanced Open Source Database, throughout the United States. <br />
<br />
The [https://postgresql.us/ official website] could use a design refresh. Your task will be to redesign one front page and one side page in Photoshop, GIMP, or some other such editing software. <br />
<br />
The requirements for the submission will be as follows:<br />
<br />
1) There should be high resolution images attached for each page (SVG, PNG, or PDF). <br />
<br />
2) Additional designs should be created for both the tablet and mobile views of the website, for both the front page and the chosen side page.<br />
<br />
3) The design should incorporate elephants in some way, in addition to using the hex color #336791 in the general color scheme. It does not need to be the primary color.<br />
<br />
4) Provide a brief summary of your logic behind the design of the webpages and your approach.<br />
<br />
=====Tags=====<br />
<br />
* User Interface<br />
* Graphics<br />
* Design<br />
* Logo<br />
* Frontend<br />
<br />
=====Categories=====<br />
<br />
User Interface<br />
<br />
==Enhancing amcheck for all AMs==<br />
<br />
=====Task Description=====<br />
<br />
Amcheck is a PostgreSQL extension to verify the integrity of index against invariants that should always hold in the valid index. This tool is designed to diagnose corruption and help developers during the implementation of new features in access methods. Currently, amcheck supports only B-tree. Also, work on GiST is in progress https://github.com/petergeoghegan/amcheck/pull/11<br />
But amcheck could be used for many other indexes: GIN, SP-GiST, BRIN, RUM.<br />
For each AM it is necessary to deduce invariants to check, implement this checks and test against various index states.<br />
Also, it would be useful to unite all AM check methods in a single entry point for checking index.<br />
The interface of check functions can also be enhanced in favor of more detailed corruption information. It would be useful to model various corruptions, including both those which can be found by data_checksums and those which cannot.<br />
<br />
The project requires a good grasp of algorithms behind very sophisticated data structures, along with concurrency and recovery over them.<br />
<br />
The expected outcome would be to introduce support for a major PostgreSQL AM in amcheck as a proposed patch.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* C<br />
* C-language<br />
* SQL<br />
* Programming<br />
* Algorithms<br />
<br />
=====Categories=====<br />
<br />
Code<br />
<br />
==Interview PostgreSQL Contributors==<br />
<br />
=====Task Description=====<br />
<br />
The purpose of this task would be for you to reach out to various PostgreSQL community contributors and perform a remote interview with one or more contributors. Some example questions could include:<br />
<br />
* how they got started with PostgreSQL<br />
* what they enjoy most about working with PostgreSQL<br />
* how they got involved in the community<br />
* what challenges are involved<br />
* how the community has evolved over time and where it is headed<br />
* what their advice is to someone looking to begin learning about PostgreSQL or contribute to the project<br />
<br />
and so on. <br />
<br />
The ultimate goal would be to develop a blogpost based on the interview that could be published through [https://planet.postgresql.org/ Planet PostgreSQL]. The result would be uploaded as a text file or PDF.<br />
<br />
The list of community contributors can be found [https://www.postgresql.org/community/contributors/ here].<br />
<br />
<br />
=====Tags=====<br />
<br />
* Blogpost<br />
* Outreach<br />
* Research<br />
* Interview<br />
* Writing<br />
<br />
=====Categories=====<br />
<br />
Outreach / Research<br />
<br />
==Review and improve the "Getting Started" tutorial in the PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a set of existing tutorials, one of which is "Getting Started". Attempt to follow this tutorial to install PostgreSQL, create a PostgreSQL database and then access that database. Make notes of issues trying to follow the tutorial, areas where the tutorial lacks specific information to be able to accomplish the task, places where the tutorial doesn't provide information about how to tell if a given step was successful or not, and other items which could be improved.<br />
<br />
Using these notes, make changes to the PostgreSQL tutorial in its source format to address the deficiencies and submit these changes as patches to the PostgreSQL source tree so that they can be included in PostgreSQL in the future. These changes must be able to be patched to the PostgreSQL source code and the resulting changes built using the PostgreSQL build tool-chain.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Review and improve the "SQL Language" tutorial in the PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a set of existing tutorials, one of which is "SQL Language". Attempt to follow this tutorial, after installing PostgreSQL and creating a database, to use and learn SQL with PostgreSQL. Make notes of issues trying to follow the tutorial, areas where the tutorial lacks specific information to be able to accomplish the task, places where the tutorial doesn't provide information about how to tell if a given step was successful or not, and other items which could be improved.<br />
<br />
Using these notes, make changes to the PostgreSQL tutorial in its source format to address the deficiencies and submit these changes as patches to the PostgreSQL source tree so that they can be included in PostgreSQL in the future. These changes must be able to be patched to the PostgreSQL source code and the resulting changes built using the PostgreSQL build tool-chain.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Review and improve the "Advanced Features" tutorial in the PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a set of existing tutorials, one of which is "Advanced Features". Attempt to follow this tutorial, after installing PostgreSQL and creating a database and learning some SQL, to work with some of the Advanced Features of PostgreSQL including creating views, foreign keys, transactions, window functions, and inheritance. Make notes of issues trying to follow the tutorial, areas where the tutorial lacks specific information to be able to accomplish the task, places where the tutorial doesn't provide information about how to tell if a given step was successful or not, and other items which could be improved.<br />
<br />
Using these notes, make changes to the PostgreSQL tutorial in its source format to address the deficiencies and submit these changes as patches to the PostgreSQL source tree so that they can be included in PostgreSQL in the future. These changes must be able to be patched to the PostgreSQL source code and the resulting changes built using the PostgreSQL build tool-chain.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Add tutorial on partitioning to PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a section for tutorials, but lacks a tutorial which covers partitioning of a PostgreSQL table.<br />
<br />
The tutorial should be in the same format as the PostgreSQL documentation and should be submitted as a patch to the PostgreSQL source code and successfully built using the PostgreSQL build tool-chain. The simplest approach to writing this documentation is to pull down the PostgreSQL source code, build all of PostgreSQL, including the documentation, then work with PostgreSQL to set up partitioning following the existing documentation and ultimately make a copy of an existing tutorial section and then rewrite it to be the partitioning tutorial.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Add tutorial on physical Replication to PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a section for tutorials, but lacks a tutorial which covers physical replication between instances.<br />
<br />
The tutorial should be in the same format as the PostgreSQL documentation and should be submitted as a patch to the PostgreSQL source code and successfully built using the PostgreSQL build tool-chain. The simplest approach to writing this documentation is to pull down the PostgreSQL source code, build all of PostgreSQL, including the documentation, then work with PostgreSQL to set up physical replication following the existing documentation and ultimately make a copy of an existing tutorial section and then rewrite it to be the physical replication tutorial.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Add tutorial on logical Replication to PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a section for tutorials, but lacks a tutorial which covers logical replication between PostgreSQL systems.<br />
<br />
The tutorial should be in the same format as the PostgreSQL documentation and should be submitted as a patch to the PostgreSQL source code and successfully built using the PostgreSQL build tool-chain. The simplest approach to writing this documentation is to pull down the PostgreSQL source code, build all of PostgreSQL, including the documentation, then work with PostgreSQL to set up logical replication following the existing documentation and ultimately make a copy of an existing tutorial section and then rewrite it to be the logical replication tutorial.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Add pg_copy utility to properly handle WAL archiving==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation uses cp as an example of an archive_command. This is not safe because cp does not sync the file or directory before returning success.<br />
<br />
Write a new utility called pg_copy that will copy a file and ensure it is durable before returning success. Existing files should not be overwritten, but the command may optionally calculate the SHA1 checksum of the destination file and return success if the source file has the same checksum.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* C<br />
* C-language<br />
* Programming<br />
<br />
=====Categories=====<br />
<br />
Code<br />
<br />
==Find & Post Job Listings==<br />
<br />
=====Task Description=====<br />
<br />
There are several entry-level technology job openings for PostgreSQL; your task would be to search for all relevant listings in your local area such as from newspapers and newspaper websites, Facebook groups, and websites of companies based in your area or those offering remote positions and compile them into a list. This list would then be provided to local high schools and community colleges in your area on their job postings board. <br />
<br />
The expected submission for this task would be the list itself as well as a list of the high schools and colleges where it was posted.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Research<br />
* Jobs<br />
<br />
=====Categories=====<br />
<br />
Outreach / Research<br />
<br />
==Help ESL Students with Job Applications==<br />
<br />
=====Task Description=====<br />
<br />
As a follow-up to "Find and Post Job Listings", you can additionally volunteer to assist with spell/grammar/language checking resumes and cover letters for ESL students applying for PostgreSQL job listings. This can extend to assisting ESL students draft their resumes. <br />
<br />
The expected submission would be the original posting advertising your services, where the posting was published (in-person at high schools/colleges, and/or online) the number of students that contacted you, and the number of students you were able to help.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Research<br />
* Jobs<br />
<br />
=====Categories=====<br />
<br />
Outreach / Research<br />
<br />
==Add autovacuum work queue view==<br />
<br />
=====Task Description=====<br />
<br />
It is not at all clear which relations the autovacuum process will work on next. It would be good to know what jobs are coming up and also the length of the queue.<br />
<br />
Add a system view that exposes the autovacuum queue so it can be queried by a system administrator. Autovacuum should also be modified to use the new system view.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* C<br />
* C-language<br />
* Programming<br />
<br />
=====Categories=====<br />
<br />
Code<br />
<br />
==Setup a Coffee Meet==<br />
<br />
=====Task Description=====<br />
<br />
Find a willing PostgreSQL contributor or committer in your area and arrange a coffee-shop meeting where young people or students of diverse backgrounds can come and have coffee with them to discuss PostgreSQL and ask questions about how to get started learning the technology. <br />
<br />
HINT: A meetup of this kind can be advertised to local audiences through [http://meetup.com/ Meetup], Facebook, Twitter (using appropriate hashtags), local high schools, or community colleges, as some examples. Try to schedule it out between 2-4 weeks in advance. <br />
<br />
The expected submission for this task would be to provide a link to the advertised meetup as well as the name of the contributor or committer that is willing to participate in the meeting. It would be preferred to include a summary of how the meeting went overall, how many attendees there were, and what kinds of questions were asked.<br />
<br />
The list of community contributors and committers can be found here:<br />
<br />
https://www.postgresql.org/community/contributors/<br />
<br />
https://wiki.postgresql.org/wiki/Committers<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Research<br />
* Jobs<br />
* Trainng<br />
* Interview<br />
<br />
=====Categories=====<br />
<br />
Outreach / Research</div>Dsteelehttps://wiki.postgresql.org/index.php?title=GCI_2018&diff=32535GCI 20182018-09-17T14:20:44Z<p>Dsteele: /* Add pg_copy utility to properly handle WAL archiving */</p>
<hr />
<div>This page is for listing tasks and collecting ideas for the yearly Google Code-in contests. <br />
<br />
https://codein.withgoogle.com/<br />
<br />
https://developers.google.com/open-source/gci/how-it-works<br />
<br />
== Regarding Project Ideas ==<br />
<br />
Project ideas are to be added here by community members.<br />
<br />
'''NOTE:''' Google looks for the following for each task:<br />
<br />
* A mix of tasks across multiple categories. (Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface)<br />
* Tasks of appropriate scope, length, and complexity.<br />
* Fully fleshed out descriptions with enough information to get started on.<br />
* Clear and understandable descriptions and titles.<br />
* Appropriate tags for searchability.<br />
<br />
Please add new sections following this format.<br />
<br />
== Mentors (2018) ==<br />
<br />
The following individuals have been listed as possible mentors on the below projects, and/or offered to be mentors for student-proposed projects:<br />
<br />
* Renee Phillips<br />
* Corey Huinker<br />
* Lætitia Avrot<br />
* Stephen Frost<br />
* Sarah Conway<br />
* Vik Fearing<br />
<br />
==Give a Local Presentation==<br />
<br />
=====Task Description=====<br />
<br />
PostgreSQL is a rapidly growing open source database, but one area that needs improvement is reaching outside of the internal community to the external open-source world to educate others about PostgreSQL and help them get started. Because of that, we can use your help to present a talk focused on PostgreSQL to an audience of your choosing. Examples would include local technology groups, technology user groups, a school, or clubs in your area. Some potential audiences can be found through Meetup: http://meetup.com/. The length of the talk can vary from a 5 minute lightning talk to a 30-60 minute long presentation or tutorial. <br />
<br />
The expected work to be uploaded will be a PDF version of the slides used during the presentation.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Research<br />
* Presentation<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Outreach/Research<br />
<br />
==Create an Educational Video==<br />
<br />
=====Task Description=====<br />
<br />
More online resources are always helpful for those learning PostgreSQL. Create a video demonstration illustrating a topic of your choosing in PostgreSQL; some examples would include a beginners introduction and history of PostgreSQL, how to get started in PostgreSQL, how to perform load balancing and high availability in a PostgreSQL cluster, how to run PostgreSQL within a Kubernetes or OpenShift environment, different monitoring statistics for your cluster, and so on.<br />
<br />
The video should be between 5-15 minutes, and must be your original work. <br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Video<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Developing a Lesson Plan==<br />
<br />
=====Task Description=====<br />
<br />
A major priority of the PostgreSQL organization is to expand awareness and education of PostgreSQL throughout the world, in a diverse and inclusive manner. One of our goals is to educate all groups, ranging from middle school, high school, and college students to adults from all ages and backgrounds, of open source technology and PostgreSQL.<br />
<br />
The expected outcome of this task is to draft sample training materials and a lesson plan for a younger age group (ranging from kids to teenagers) on getting started with PostgreSQL. It should be fun and engaging, with interactive tasks for hands-on learning. This can be submitted in any format, ranging from slides to a document-based format. The lesson plan should be prefaced with the intended audience, the difficulty level, and the estimated amount of time to complete the training. <br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Research<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Outreach/Research<br />
<br />
==Design a Logo for a Conference==<br />
<br />
=====Task Description=====<br />
<br />
PostgreSQL has several conferences that revolve around educating and discussing PostgreSQL within the community. One of these conferences, Postgres Open SV 2019, is in need of a new, updated, and high-resolution logo for next year's conference. The website from 2018 with the currently existing logo can be found here:<br />
<br />
https://2018.postgresopen.org/<br />
<br />
The requirements are as follows:<br />
<br />
1) Submissions should be high-resolution (PNG or SVG) and should include a source file.<br />
<br />
2) The logo should resonate well with the current website design, as next year's design will be similar to the existing.<br />
<br />
3) While it does not need to resemble the current logo, it does need to center around an elephant as the theme. The reasoning for this is the official logo for PostgreSQL itself is an elephant: https://www.postgresql.org/media/img/about/press/elephant.png<br />
<br />
4) Provide a brief summary of your logic behind the design of the logo and your approach.<br />
<br />
=====Tags=====<br />
<br />
* User Interface<br />
* Graphics<br />
* Design<br />
* Logo<br />
<br />
=====Categories=====<br />
<br />
User Interface<br />
<br />
==Reviewing Patches==<br />
<br />
=====Task Description=====<br />
<br />
PostgreSQL development revolves around [[CommitFest]] periods where any and all volunteers are needed to assist in reviewing proposed patches. Your task would be to select an open patch, evaluate it, and ensure it does what the author intends. <br />
<br />
Please demonstrate your testing process and include screenshots of the steps taken, along with the proof that it is working, in a document that will be submitted for evaluation as proof of completing the task.<br />
<br />
More information can be found here:<br />
<br />
https://wiki.postgresql.org/wiki/Reviewing_a_Patch<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* SQL<br />
* Databases<br />
* C<br />
* C-language<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
==Improve PostgreSQL Regression Test Coverage==<br />
<br />
=====Task Description=====<br />
<br />
PostgreSQL can use additional development in the area of regression tests. Regression testing ensures that within PostgreSQL, new changes and additions aren't breaking existing functionality. Your task will be to introduce new regression tests for command line utilities and extensions that are poorly covered, as shown on https://coverage.postgresql.org/. <br />
<br />
The current regression test coverage for PostgreSQL isn't great, to the point where some areas of the code are covered only at single-digit-percent levels.<br />
<br />
Having good regression tests for such an important project as PostgreSQL is really key to minimizing the chance that any regressions are introduced. PostgreSQL's build system includes a "make coverage-html" to generate the report.<br />
<br />
Please note that this project involves writing SQL code and Perl code, at a minimum, to implement the tests necessary to increase the code coverage of the PostgreSQL regression tests.<br />
<br />
More information can be found in the [https://www.postgresql.org/docs/10/static/regress.html official documentation] on regression tasks.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* SQL<br />
* Perl<br />
* Databases<br />
* C<br />
* C-language<br />
* Development<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
==pgAdmin 4 Bug - Setting up SMTP with Docker==<br />
<br />
=====Task Description=====<br />
<br />
There is no currently existing documentation for setting up SMTP when running the official Docker image for pgAdmin 4. Without SMTP, users cannot change their password or use the "forgot password" option. The expected outcome from this task would be to determine how to configure SMTP with the Docker container and write up documentation illustrating the steps. <br />
<br />
A requirement would be to create a PostgreSQL community account. The resulting documentation would be sent in to the pgadmin4-hackers mailing list for review, and uploaded as a file for proof of completion. https://www.postgresql.org/list/pgadmin-hackers/<br />
<br />
The original bug report can be found here: https://redmine.postgresql.org/issues/3599<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* SQL<br />
* Databases<br />
* Development<br />
* Documentation<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
Documentation / Training<br />
<br />
==PostGIS Bug - Windows Installer==<br />
<br />
=====Task Description=====<br />
<br />
When installing PostGIS on Microsoft Windows, the installer shows a "Database Connection Information" dialog to supply User Name, Password, and Port. The installer will begin to install PostGIS, however, if there is a mistake in the connection information, the installer fails part-way in, requiring it to be run again from the beginning.<br />
<br />
It would be nice to allow multiple attempts to correct the connection information, if say, there was a typo with the password. This way the installer only needs to be run once (for example, using Application Stack Builder, which downloads the installer to %TEMP%).<br />
<br />
Not only should the connection info establish a connection to a database, but select count(*)=1 from pg_user where usename=$1 and usecreatedb;. If there is an error, the user should be able to go back and correct, try again, repeat or cancel. Correct connection info should be established before starting the install process.<br />
<br />
A requirement would be to create a PostgreSQL community account. The resulting documentation would be sent in to the postgis-devel mailing list for review, and uploaded as a file for proof of completion. https://lists.osgeo.org/mailman/listinfo/postgis-devel<br />
<br />
The original bug report can be found here: https://trac.osgeo.org/postgis/ticket/516<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* Authentication<br />
* SQL<br />
* Databases<br />
* Development<br />
* Documentation<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
Documentation / Training<br />
<br />
==Participate in Mailing Lists==<br />
<br />
=====Task Description=====<br />
<br />
The purpose of this task is to introduce you to community involvement and participation. The first required step will be to create a community account if you do not already have one (https://www.postgresql.org/account/signup/) and subscribe to the pgsql-bugs mailing list (https://www.postgresql.org/list/). <br />
<br />
Secondly, you will need to participate in a mailing list thread when a user reports a bug through reproducing their reported bug and responding to the community thread confirming the existence of the bug. Include the operating system and version of PostgreSQL you are running, in addition to the steps taken to reproduce the original issue. <br />
<br />
The expected submission for this task will be a link to the mailing list archive for the relevant thread and a screenshot of the reproduced problem on your machine, showing the problem reported by the original user.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Review<br />
* Bug fixing<br />
* Patch<br />
* Quality Assurance<br />
* SQL<br />
* Databases<br />
* Development<br />
* Testing<br />
<br />
=====Categories=====<br />
<br />
Quality Assurance<br />
<br />
Code<br />
<br />
User Interface<br />
<br />
==PostgreSQL US - Develop an Integrated Form==<br />
<br />
=====Task Description=====<br />
<br />
The United States PostgreSQL Association, affectionately known as PgUS, is a IRS 501(c)(3) non-profit public charity that has the intention of supporting the growth and education of PostgreSQL, The World's Most Advanced Open Source Database, throughout the United States. <br />
<br />
Your task will be to fork the [https://github.com/pg-us/pgusweb official repository] hosting the PostgreSQL US website and propose a patch / pull request that integrates the currently existing Diversity Scholarship form hosted [https://docs.google.com/forms/d/1dgFUVXHgJ0sLAETJaAciLFetvFq5_S0-juZ3g8QyeVc/edit?ts=58f14198 on Google Forms] into a web page of its own.<br />
<br />
A further description of the Diversity Scholarship and its purpose can be found [https://postgresql.us/diversity/ here].<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Design<br />
* User Interface<br />
* HTML<br />
* CSS<br />
* Bootstrap<br />
<br />
=====Categories=====<br />
<br />
Code<br />
<br />
User Interface<br />
<br />
==PostgreSQL US - Develop a Resolution Tracker==<br />
<br />
=====Task Description=====<br />
<br />
The United States PostgreSQL Association, affectionately known as PgUS, is a IRS 501(c)(3) non-profit public charity that has the intention of supporting the growth and education of PostgreSQL, The World's Most Advanced Open Source Database, throughout the United States. <br />
<br />
Your task will be to fork the [https://github.com/pg-us/pgusweb official repository] hosting the PostgreSQL US website and propose a patch / pull request that contains a form in which board members can record resolutions in addition to information relating to who voted on the resolution, what the resolution is along with a description, and what the resulting votes are.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* Design<br />
* User Interface<br />
* HTML<br />
* CSS<br />
* Bootstrap<br />
<br />
=====Categories=====<br />
<br />
Code<br />
<br />
User Interface<br />
<br />
==Enhancing amcheck for all AMs==<br />
<br />
=====Task Description=====<br />
<br />
Amcheck is a PostgreSQL extension to verify the integrity of index against invariants that should always hold in the valid index. This tool is designed to diagnose corruption and help developers during the implementation of new features in access methods. Currently, amcheck supports only B-tree. Also, work on GiST is in progress https://github.com/petergeoghegan/amcheck/pull/11<br />
But amcheck could be used for many other indexes: GIN, SP-GiST, BRIN, RUM.<br />
For each AM it is necessary to deduce invariants to check, implement this checks and test against various index states.<br />
Also, it would be useful to unite all AM check methods in a single entry point for checking index.<br />
The interface of check functions can also be enhanced in favor of more detailed corruption information. It would be useful to model various corruptions, including both those which can be found by data_checksums and those which cannot.<br />
<br />
The project requires a good grasp of algorithms behind very sophisticated data structures, along with concurrency and recovery over them.<br />
<br />
The expected outcome would be to introduce support for a major PostgreSQL AM in amcheck as a proposed patch.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* C<br />
* C-language<br />
* SQL<br />
* Programming<br />
* Algorithms<br />
<br />
=====Categories=====<br />
<br />
Code<br />
<br />
==Interview PostgreSQL Contributors==<br />
<br />
=====Task Description=====<br />
<br />
The purpose of this task would be for you to reach out to various PostgreSQL community contributors and perform a remote interview with one or more contributors. Some example questions could include:<br />
<br />
* how they got started with PostgreSQL<br />
* what they enjoy most about working with PostgreSQL<br />
* how they got involved in the community<br />
* what challenges are involved<br />
* how the community has evolved over time and where it is headed<br />
* what their advice is to someone looking to begin learning about PostgreSQL or contribute to the project<br />
<br />
and so on. <br />
<br />
The ultimate goal would be to develop a blogpost based on the interview that could be published through [https://planet.postgresql.org/ Planet PostgreSQL]. The result would be uploaded as a text file or PDF.<br />
<br />
The list of community contributors can be found [https://www.postgresql.org/community/contributors/ here].<br />
<br />
<br />
=====Tags=====<br />
<br />
* Blogpost<br />
* Outreach<br />
* Research<br />
* Interview<br />
* Writing<br />
<br />
=====Categories=====<br />
<br />
Outreach / Research<br />
<br />
==Review and improve the "Getting Started" tutorial in the PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a set of existing tutorials, one of which is "Getting Started". Attempt to follow this tutorial to install PostgreSQL, create a PostgreSQL database and then access that database. Make notes of issues trying to follow the tutorial, areas where the tutorial lacks specific information to be able to accomplish the task, places where the tutorial doesn't provide information about how to tell if a given step was successful or not, and other items which could be improved.<br />
<br />
Using these notes, make changes to the PostgreSQL tutorial in its source format to address the deficiencies and submit these changes as patches to the PostgreSQL source tree so that they can be included in PostgreSQL in the future. These changes must be able to be patched to the PostgreSQL source code and the resulting changes built using the PostgreSQL build tool-chain.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Review and improve the "SQL Language" tutorial in the PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a set of existing tutorials, one of which is "SQL Language". Attempt to follow this tutorial, after installing PostgreSQL and creating a database, to use and learn SQL with PostgreSQL. Make notes of issues trying to follow the tutorial, areas where the tutorial lacks specific information to be able to accomplish the task, places where the tutorial doesn't provide information about how to tell if a given step was successful or not, and other items which could be improved.<br />
<br />
Using these notes, make changes to the PostgreSQL tutorial in its source format to address the deficiencies and submit these changes as patches to the PostgreSQL source tree so that they can be included in PostgreSQL in the future. These changes must be able to be patched to the PostgreSQL source code and the resulting changes built using the PostgreSQL build tool-chain.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Review and improve the "Advanced Features" tutorial in the PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a set of existing tutorials, one of which is "Advanced Features". Attempt to follow this tutorial, after installing PostgreSQL and creating a database and learning some SQL, to work with some of the Advanced Features of PostgreSQL including creating views, foreign keys, transactions, window functions, and inheritance. Make notes of issues trying to follow the tutorial, areas where the tutorial lacks specific information to be able to accomplish the task, places where the tutorial doesn't provide information about how to tell if a given step was successful or not, and other items which could be improved.<br />
<br />
Using these notes, make changes to the PostgreSQL tutorial in its source format to address the deficiencies and submit these changes as patches to the PostgreSQL source tree so that they can be included in PostgreSQL in the future. These changes must be able to be patched to the PostgreSQL source code and the resulting changes built using the PostgreSQL build tool-chain.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Add tutorial on partitioning to PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a section for tutorials, but lacks a tutorial which covers partitioning of a PostgreSQL table.<br />
<br />
The tutorial should be in the same format as the PostgreSQL documentation and should be submitted as a patch to the PostgreSQL source code and successfully built using the PostgreSQL build tool-chain. The simplest approach to writing this documentation is to pull down the PostgreSQL source code, build all of PostgreSQL, including the documentation, then work with PostgreSQL to set up partitioning following the existing documentation and ultimately make a copy of an existing tutorial section and then rewrite it to be the partitioning tutorial.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Add tutorial on physical Replication to PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a section for tutorials, but lacks a tutorial which covers physical replication between instances.<br />
<br />
The tutorial should be in the same format as the PostgreSQL documentation and should be submitted as a patch to the PostgreSQL source code and successfully built using the PostgreSQL build tool-chain. The simplest approach to writing this documentation is to pull down the PostgreSQL source code, build all of PostgreSQL, including the documentation, then work with PostgreSQL to set up physical replication following the existing documentation and ultimately make a copy of an existing tutorial section and then rewrite it to be the physical replication tutorial.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Add tutorial on logical Replication to PostgreSQL Documentation==<br />
<br />
=====Task Description=====<br />
<br />
The PostgreSQL documentation has a section for tutorials, but lacks a tutorial which covers logical replication between PostgreSQL systems.<br />
<br />
The tutorial should be in the same format as the PostgreSQL documentation and should be submitted as a patch to the PostgreSQL source code and successfully built using the PostgreSQL build tool-chain. The simplest approach to writing this documentation is to pull down the PostgreSQL source code, build all of PostgreSQL, including the documentation, then work with PostgreSQL to set up logical replication following the existing documentation and ultimately make a copy of an existing tutorial section and then rewrite it to be the logical replication tutorial.<br />
<br />
=====Tags=====<br />
<br />
* Outreach<br />
* Documentation<br />
* Tutorial<br />
* Training<br />
* SQL<br />
* Databases<br />
<br />
=====Categories=====<br />
<br />
Documentation/Training<br />
<br />
==Add pg_copy utility to properly handle WAL archiving==<br />
<br />
The PostgreSQL documentation uses cp as an example of an archive_command. This is not safe because cp does not sync the file or directory before returning success.<br />
<br />
Write a new utility called pg_copy that will copy a file and ensure it is durable before returning success. Existing files should not be overwritten, but the command may optionally calculate the SHA1 checksum of the destination file and return success if the source file has the same checksum.<br />
<br />
=====Tags=====<br />
<br />
* Code<br />
* C<br />
* C-language<br />
* Programming<br />
<br />
=====Categories=====<br />
<br />
Code</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PgCon_2018_Developer_Meeting&diff=31522PgCon 2018 Developer Meeting2018-02-26T14:05:43Z<p>Dsteele: /* RSVPs */</p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Tuesday 29 May, 2018 at the University of Ottawa, prior to pgCon 2018. In order to keep the numbers manageable, this meeting is by '''invitation only'''. Unfortunately it is quite possible that we've overlooked important individuals 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).<br />
<br />
Please note that 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 11/10 release cycles. We have not invited any contributors based on their contributions to related projects, or seniority in regional user groups or sponsoring companies.<br />
<br />
As at last years event, an Unconference will be held on Wednesday for in-depth discussion of technical topics.<br />
<br />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Define the schedule for the 12.0 release cycle<br />
* Address any proposed timing, policy, or procedure issues<br />
* Address any proposed [http://en.wikipedia.org/wiki/Wicked_problem Wicked problems]<br />
<br />
== Time & Location ==<br />
<br />
The meeting will be:<br />
<br />
* 9:00AM to 12PM<br />
* TBD<br />
* University of Ottawa.<br />
<br />
Coffee, tea and snacks will be served starting at 8:45am. Lunch will be after the meeting.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname):<br />
<br />
* Magnus Hagander<br />
* Tatsuo Ishii<br />
* Amit Kapila<br />
* Thomas Munro<br />
* Michael Paquier<br />
* David Steele<br />
<br />
== Agenda Items ==<br />
<br />
* 12.0 release and commitfest schedule (Dave)<br />
<br />
* ''Please add suggestions for agenda items here. (with your name)''<br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:30<br />
|Welcome and introductions<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:30 - 10:45<br />
|Coffee break<br />
|All<br />
<br />
|- <br />
|11:50 - 12:00<br />
|Any other business<br />
|Dave Page<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:00<br />
|Lunch<br />
|<br />
<br />
|}<br />
<br />
== Minutes ==<br />
<br />
=== Welcome and introductions ===<br />
<br />
Attendees:<br />
<br />
=== 12.0 release and commitfest schedule ===<br />
<br />
=== Any other business ===</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Binary_Replication_Tools&diff=30994Binary Replication Tools2017-10-10T17:27:07Z<p>Dsteele: /* pgBackRest */ Add S3 support.</p>
<hr />
<div>= Disclaimer =<br />
<br />
This is a Work-In-Progress, started Dec 28, 2012.<br />
<br />
Additions welcome, and [[User:Selena|Selena]] reserves the right to edit. :)<br />
<br />
= Purpose = <br />
<br />
Compare binary replication tools for PostgreSQL for features and ease of use. This document should classify and differentiate binary replication tools for easier selection and fit to purpose.<br />
<br />
== Comparison Matrix ==<br />
<br />
{|border=1<br />
!Tool!!Documentation!!License!!Makes base backups!!Makes base backups from replicas!!Manages backups!!Creates replicas!!Monitors replication delay!!Supports automated failover!!Transport used!!Source includes replication tests<br />
|- style="background-color:#ffffcc;"<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html pg_basebackup]*<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html Postgres docs]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| No<br />
| No<br />
| PostgreSQL connection<br />
|<br />
|-<br />
| [http://www.pgbackrest.org/ pgBackRest] <br />
| [http://www.pgbackrest.org/user-guide.html Documentation]<br />
| MIT<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| ssh<br />
| Yes<br />
<br />
|-<br />
| [http://www.pgbarman.org/ pgbarman] <br />
| [http://docs.pgbarman.org/ Documentation]<br />
| GPLv3<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| Yes<br />
| No<br />
| rsync/ssh, pg_basebackup<br />
|<br />
|-<br />
| [https://github.com/omniti-labs/omnipitr OmniPITR]<br />
| [https://github.com/omniti-labs/omnipitr/blob/master/doc/intro.pod Intro]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| WAL archive delay<br />
| No<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/ohmu/pghoard pghoard]<br />
| [https://github.com/ohmu/pghoard/blob/master/README.rst Readme]<br />
| Apache<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Yes<br />
| No<br />
| No<br />
| AWS S3, Azure, Ceph, Google Cloud Storage<br />
| Yes<br />
|-<br />
| [http://code.google.com/p/pg-rman/ pg-rman] <br />
| [http://code.google.com/p/pg-rman/wiki/readme Readme]<br />
| BSD<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| local / NFS mount<br />
|<br />
|-<br />
| [http://www.repmgr.org/ repmgr]<br />
| [https://github.com/2ndQuadrant/repmgr#readme Readme]<br />
| GPLv3<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| Yes<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/markokr/skytools Skytools]<br />
| [https://github.com/markokr/skytools/blob/master/doc/walmgr3.txt walmgr3]<br />
| BSD-ish<br />
|<br />
|-<br />
| [https://github.com/wal-e/WAL-E WAL-E]<br />
| [https://github.com/wal-e/WAL-E#readme Readme]<br />
| BSD<br />
| Yes<br />
| No<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| HTTPS/SSL<br />
| <br />
|-<br />
|}<br />
<br />
* pg_basebackup is included with a standard PostgreSQL installation.<br />
<br />
<br />
'''Tool''': name of the project that manages binary replication or WAL archiving<br />
<br />
'''Documentation''': Link to canonical documentation for the project. Several projects have broken links that show up as top results in Google.<br />
<br />
'''License''': License software is released under. So far, we only have open/free software projects listed. We could add commercial projects.<br />
<br />
'''Makes base backups''': Yes if the project supports creating binary archives, including the necessary WAL to restore a backed-up instance.<br />
<br />
'''Makes base backups from replicas''': Yes if the project supports creating binary archives and WAL using the PGDATA directory from a replica rather than the master database.<br />
<br />
'''Manages backups''': Yes if the project adds, removes and lists binary archives.<br />
<br />
'''Creates replicas''': Yes if the project automatically adds a recovery.conf (sets up replication) as part of restoring a base backup.<br />
<br />
'''Monitors replication delay''': Yes if the project supports monitoring of replication delay (WAL shipping or streaming replication).<br />
<br />
'''Supports automated failover''': Yes if the project has an option for detecting master failure and promoting a replica to master.<br />
<br />
'''Transport used''': Supported methods for file transfer for making backups or replicas<br />
<br />
= Barman = <br />
<br />
[http://www.pgbarman.org/ pgbarman] [https://github.com/selenamarie/pg_replication_demo/tree/master/barman Demo setup for pgbarman]<br />
<br />
Summary of features: <br />
* Creates base backups<br />
* Uses SSH as transport for backup<br />
* Configuration stored in file or command-line<br />
* Restore is automatable for creating replicas, although not explictly supported<br />
* GPLv3<br />
<br />
Install notes: <br />
* Had a dependency problem with 9.1 on Ubuntu Precise, so installed from source<br />
* Missing dep for argcomplete, noted in README in demo repo<br />
* written in Python<br />
<br />
= OmniPITR = <br />
<br />
[https://github.com/omniti-labs/omnipitr OmniPITR]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/omnipitr Demo of a simple replication setup with OmniPITR]<br />
<br />
Summary of Features:<br />
* Creating PITR backups from Master or Slave<br />
* Restoring a PITR backup for DR<br />
* Creating replicas (by untarring backups)<br />
* Monitoring of replicas<br />
* Supports 'pause removal' of WAL during a backup (nice!)<br />
* PostgreSQL license<br />
<br />
Install notes: <br />
* No packaging, perl <br />
* No documented support for streaming replication<br />
* Uses '^' instead of '%' in custom logfile naming<br />
* No configuration file option (instead of using long command-line options)<br />
* Supported on all Linux, Solaris variants<br />
<br />
= pgBackRest =<br />
<br />
[http://www.pgbackrest.org/ pgBackRest]<br />
<br />
Summary of features: <br />
* Parallel Backup & Restore<br />
* Local or Remote Operation<br />
* Full, Incremental, & Differential Backups<br />
* Backup & Archive Expiration<br />
* Backup Resume<br />
* Streaming Compression & Checksums<br />
* Delta Restore<br />
* Parallel WAL Archiving<br />
* Tablespace & Link Support<br />
* Compatibility with PostgreSQL >= 8.3<br />
* S3 Support<br />
<br />
= pghoard =<br />
<br />
https://github.com/ohmu/pghoard<br />
<br />
Summary of features:<br />
* Stores basebackups and WAL to cloud object stores (AWS S3, Azure, Ceph, Google Cloud)<br />
* Restore existing basebackups and setup a new cluster with a recovery.conf pointing to another master database<br />
* Create scheduled basebackups<br />
* Can be used as archive_command to archive WALs in the object store<br />
* Can be used as restore_command to restore WALs from the object store<br />
* Basebackup and WAL compression using LZMA<br />
* Optionally encrypts backups<br />
* Supports PITR using timestamps, names and xids<br />
<br />
Install notes:<br />
* Written in Python, includes Debian and Fedora packaging scripts<br />
* 'pghoard' daemon manages basebackups and cleans up WALs<br />
* 'pghoard_archive_command' and 'pghoard_restore' access the locally running 'pghoard' daemon to store and restore files<br />
<br />
= pg-rman =<br />
<br />
[http://code.google.com/p/pg-rman/ pg-rman] [https://github.com/selenamarie/pg_replication_demo/tree/master/pgrman Simple demo for pg_rman setup]<br />
<br />
Summary of features: <br />
* Online backup and recovery, including backup from a replica<br />
* Archive management and restore<br />
* .ini configuration file<br />
* Simple command-line options<br />
<br />
Install notes: <br />
* Written in C, install with 'make USE_PGXS=1'<br />
* On Ubuntu/Debian, installs in non-default bin directory<br />
* Commands are simple, manages WAL archive as well as backups<br />
<br />
<br />
= repmgr =<br />
<br />
[http://www.repmgr.org/ repmgr]<br />
[https://github.com/2ndQuadrant/repmgr GitHub repository]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/repmgr Demo of a simple setup with repmgr]<br />
<br />
Supported features:<br />
* Setting up new replicas/hot_standby with streaming replication (makes recovery.conf itself)<br />
* Making base backups<br />
* Failover (automated, or not, including redirecting replicas to connect to a new master after failover)<br />
* Lag monitoring (repmgrd)<br />
* A "witness" DB server for monitoring (typically on a replica)<br />
* License: GPLv3<br />
<br />
Install notes: <br />
* Written in C<br />
* Developed on Debian systems, so support for package is present. [https://launchpad.net/repmgr Ubuntu packages] are available since Trusty (14.04).<br />
* Otherwise, installs like a typical UNIX utility out of postgresql/contrib source tree (make USE_PGXS=1; make USE_PGXS=1 install)<br />
* Detailed docs are in [https://github.com/2ndQuadrant/repmgr the README] for installing on many Linux platforms<br />
* Doesn't appear to be supported on Mac OS X<br />
<br />
= Skytools / walmgr =<br />
<br />
[https://github.com/markokr/skytools Skytools]<br />
<br />
= WAL-E =<br />
<br />
[https://github.com/wal-e/wal-e WAL-E]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Binary_Replication_Tools&diff=29812Binary Replication Tools2017-04-10T01:37:30Z<p>Dsteele: /* pghoard */</p>
<hr />
<div>= Disclaimer =<br />
<br />
This is a Work-In-Progress, started Dec 28, 2012.<br />
<br />
Additions welcome, and [[User:Selena|Selena]] reserves the right to edit. :)<br />
<br />
= Purpose = <br />
<br />
Compare binary replication tools for PostgreSQL for features and ease of use. This document should classify and differentiate binary replication tools for easier selection and fit to purpose.<br />
<br />
== Comparison Matrix ==<br />
<br />
{|border=1<br />
!Tool!!Documentation!!License!!Makes base backups!!Makes base backups from replicas!!Manages backups!!Creates replicas!!Monitors replication delay!!Supports automated failover!!Transport used!!Source includes replication tests<br />
|- style="background-color:#ffffcc;"<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html pg_basebackup]*<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html Postgres docs]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| No<br />
| No<br />
| PostgreSQL connection<br />
|<br />
|-<br />
| [http://www.pgbackrest.org/ pgBackRest] <br />
| [http://www.pgbackrest.org/user-guide.html Documentation]<br />
| MIT<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| ssh<br />
| Yes<br />
<br />
|-<br />
| [http://www.pgbarman.org/ pgbarman] <br />
| [http://docs.pgbarman.org/ Documentation]<br />
| GPLv3<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| Yes<br />
| No<br />
| rsync/ssh, pg_basebackup<br />
|<br />
|-<br />
| [https://github.com/omniti-labs/omnipitr OmniPITR]<br />
| [https://github.com/omniti-labs/omnipitr/blob/master/doc/intro.pod Intro]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| WAL archive delay<br />
| No<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/ohmu/pghoard pghoard]<br />
| [https://github.com/ohmu/pghoard/blob/master/README.rst Readme]<br />
| Apache<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Yes<br />
| No<br />
| No<br />
| AWS S3, Azure, Ceph, Google Cloud Storage<br />
| Yes<br />
|-<br />
| [http://code.google.com/p/pg-rman/ pg-rman] <br />
| [http://code.google.com/p/pg-rman/wiki/readme Readme]<br />
| BSD<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| local / NFS mount<br />
|<br />
|-<br />
| [http://www.repmgr.org/ repmgr]<br />
| [https://github.com/2ndQuadrant/repmgr#readme Readme]<br />
| GPLv3<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| Yes<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/markokr/skytools Skytools]<br />
| [https://github.com/markokr/skytools/blob/master/doc/walmgr3.txt walmgr3]<br />
| BSD-ish<br />
|<br />
|-<br />
| [https://github.com/wal-e/WAL-E WAL-E]<br />
| [https://github.com/wal-e/WAL-E#readme Readme]<br />
| BSD<br />
| Yes<br />
| No<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| HTTPS/SSL<br />
| <br />
|-<br />
|}<br />
<br />
* pg_basebackup is included with a standard PostgreSQL installation.<br />
<br />
<br />
'''Tool''': name of the project that manages binary replication or WAL archiving<br />
<br />
'''Documentation''': Link to canonical documentation for the project. Several projects have broken links that show up as top results in Google.<br />
<br />
'''License''': License software is released under. So far, we only have open/free software projects listed. We could add commercial projects.<br />
<br />
'''Makes base backups''': Yes if the project supports creating binary archives, including the necessary WAL to restore a backed-up instance.<br />
<br />
'''Makes base backups from replicas''': Yes if the project supports creating binary archives and WAL using the PGDATA directory from a replica rather than the master database.<br />
<br />
'''Manages backups''': Yes if the project adds, removes and lists binary archives.<br />
<br />
'''Creates replicas''': Yes if the project automatically adds a recovery.conf (sets up replication) as part of restoring a base backup.<br />
<br />
'''Monitors replication delay''': Yes if the project supports monitoring of replication delay (WAL shipping or streaming replication).<br />
<br />
'''Supports automated failover''': Yes if the project has an option for detecting master failure and promoting a replica to master.<br />
<br />
'''Transport used''': Supported methods for file transfer for making backups or replicas<br />
<br />
= Barman = <br />
<br />
[http://www.pgbarman.org/ pgbarman] [https://github.com/selenamarie/pg_replication_demo/tree/master/barman Demo setup for pgbarman]<br />
<br />
Summary of features: <br />
* Creates base backups<br />
* Uses SSH as transport for backup<br />
* Configuration stored in file or command-line<br />
* Restore is automatable for creating replicas, although not explictly supported<br />
* GPLv3<br />
<br />
Install notes: <br />
* Had a dependency problem with 9.1 on Ubuntu Precise, so installed from source<br />
* Missing dep for argcomplete, noted in README in demo repo<br />
* written in Python<br />
<br />
= OmniPITR = <br />
<br />
[https://github.com/omniti-labs/omnipitr OmniPITR]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/omnipitr Demo of a simple replication setup with OmniPITR]<br />
<br />
Summary of Features:<br />
* Creating PITR backups from Master or Slave<br />
* Restoring a PITR backup for DR<br />
* Creating replicas (by untarring backups)<br />
* Monitoring of replicas<br />
* Supports 'pause removal' of WAL during a backup (nice!)<br />
* PostgreSQL license<br />
<br />
Install notes: <br />
* No packaging, perl <br />
* No documented support for streaming replication<br />
* Uses '^' instead of '%' in custom logfile naming<br />
* No configuration file option (instead of using long command-line options)<br />
* Supported on all Linux, Solaris variants<br />
<br />
= pgBackRest =<br />
<br />
[http://www.pgbackrest.org/ pgBackRest]<br />
<br />
Summary of features: <br />
* Parallel Backup & Restore<br />
* Local or Remote Operation<br />
* Full, Incremental, & Differential Backups<br />
* Backup & Archive Expiration<br />
* Backup Resume<br />
* Streaming Compression & Checksums<br />
* Delta Restore<br />
* Parallel WAL Archiving<br />
* Tablespace & Link Support<br />
* Compatibility with PostgreSQL >= 8.3<br />
<br />
= pghoard =<br />
<br />
https://github.com/ohmu/pghoard<br />
<br />
Summary of features:<br />
* Stores basebackups and WAL to cloud object stores (AWS S3, Azure, Ceph, Google Cloud)<br />
* Restore existing basebackups and setup a new cluster with a recovery.conf pointing to another master database<br />
* Create scheduled basebackups<br />
* Can be used as archive_command to archive WALs in the object store<br />
* Can be used as restore_command to restore WALs from the object store<br />
* Basebackup and WAL compression using LZMA<br />
* Optionally encrypts backups<br />
* Supports PITR using timestamps, names and xids<br />
<br />
Install notes:<br />
* Written in Python, includes Debian and Fedora packaging scripts<br />
* 'pghoard' daemon manages basebackups and cleans up WALs<br />
* 'pghoard_archive_command' and 'pghoard_restore' access the locally running 'pghoard' daemon to store and restore files<br />
<br />
= pg-rman =<br />
<br />
[http://code.google.com/p/pg-rman/ pg-rman] [https://github.com/selenamarie/pg_replication_demo/tree/master/pgrman Simple demo for pg_rman setup]<br />
<br />
Summary of features: <br />
* Online backup and recovery, including backup from a replica<br />
* Archive management and restore<br />
* .ini configuration file<br />
* Simple command-line options<br />
<br />
Install notes: <br />
* Written in C, install with 'make USE_PGXS=1'<br />
* On Ubuntu/Debian, installs in non-default bin directory<br />
* Commands are simple, manages WAL archive as well as backups<br />
<br />
<br />
= repmgr =<br />
<br />
[http://www.repmgr.org/ repmgr]<br />
[https://github.com/2ndQuadrant/repmgr GitHub repository]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/repmgr Demo of a simple setup with repmgr]<br />
<br />
Supported features:<br />
* Setting up new replicas/hot_standby with streaming replication (makes recovery.conf itself)<br />
* Making base backups<br />
* Failover (automated, or not, including redirecting replicas to connect to a new master after failover)<br />
* Lag monitoring (repmgrd)<br />
* A "witness" DB server for monitoring (typically on a replica)<br />
* License: GPLv3<br />
<br />
Install notes: <br />
* Written in C<br />
* Developed on Debian systems, so support for package is present. [https://launchpad.net/repmgr Ubuntu packages] are available since Trusty (14.04).<br />
* Otherwise, installs like a typical UNIX utility out of postgresql/contrib source tree (make USE_PGXS=1; make USE_PGXS=1 install)<br />
* Detailed docs are in [https://github.com/2ndQuadrant/repmgr the README] for installing on many Linux platforms<br />
* Doesn't appear to be supported on Mac OS X<br />
<br />
= Skytools / walmgr =<br />
<br />
[https://github.com/markokr/skytools Skytools]<br />
<br />
= WAL-E =<br />
<br />
[https://github.com/wal-e/wal-e WAL-E]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Binary_Replication_Tools&diff=29811Binary Replication Tools2017-04-10T01:37:19Z<p>Dsteele: /* pgBackRest */</p>
<hr />
<div>= Disclaimer =<br />
<br />
This is a Work-In-Progress, started Dec 28, 2012.<br />
<br />
Additions welcome, and [[User:Selena|Selena]] reserves the right to edit. :)<br />
<br />
= Purpose = <br />
<br />
Compare binary replication tools for PostgreSQL for features and ease of use. This document should classify and differentiate binary replication tools for easier selection and fit to purpose.<br />
<br />
== Comparison Matrix ==<br />
<br />
{|border=1<br />
!Tool!!Documentation!!License!!Makes base backups!!Makes base backups from replicas!!Manages backups!!Creates replicas!!Monitors replication delay!!Supports automated failover!!Transport used!!Source includes replication tests<br />
|- style="background-color:#ffffcc;"<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html pg_basebackup]*<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html Postgres docs]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| No<br />
| No<br />
| PostgreSQL connection<br />
|<br />
|-<br />
| [http://www.pgbackrest.org/ pgBackRest] <br />
| [http://www.pgbackrest.org/user-guide.html Documentation]<br />
| MIT<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| ssh<br />
| Yes<br />
<br />
|-<br />
| [http://www.pgbarman.org/ pgbarman] <br />
| [http://docs.pgbarman.org/ Documentation]<br />
| GPLv3<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| Yes<br />
| No<br />
| rsync/ssh, pg_basebackup<br />
|<br />
|-<br />
| [https://github.com/omniti-labs/omnipitr OmniPITR]<br />
| [https://github.com/omniti-labs/omnipitr/blob/master/doc/intro.pod Intro]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| WAL archive delay<br />
| No<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/ohmu/pghoard pghoard]<br />
| [https://github.com/ohmu/pghoard/blob/master/README.rst Readme]<br />
| Apache<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Yes<br />
| No<br />
| No<br />
| AWS S3, Azure, Ceph, Google Cloud Storage<br />
| Yes<br />
|-<br />
| [http://code.google.com/p/pg-rman/ pg-rman] <br />
| [http://code.google.com/p/pg-rman/wiki/readme Readme]<br />
| BSD<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| local / NFS mount<br />
|<br />
|-<br />
| [http://www.repmgr.org/ repmgr]<br />
| [https://github.com/2ndQuadrant/repmgr#readme Readme]<br />
| GPLv3<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| Yes<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/markokr/skytools Skytools]<br />
| [https://github.com/markokr/skytools/blob/master/doc/walmgr3.txt walmgr3]<br />
| BSD-ish<br />
|<br />
|-<br />
| [https://github.com/wal-e/WAL-E WAL-E]<br />
| [https://github.com/wal-e/WAL-E#readme Readme]<br />
| BSD<br />
| Yes<br />
| No<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| HTTPS/SSL<br />
| <br />
|-<br />
|}<br />
<br />
* pg_basebackup is included with a standard PostgreSQL installation.<br />
<br />
<br />
'''Tool''': name of the project that manages binary replication or WAL archiving<br />
<br />
'''Documentation''': Link to canonical documentation for the project. Several projects have broken links that show up as top results in Google.<br />
<br />
'''License''': License software is released under. So far, we only have open/free software projects listed. We could add commercial projects.<br />
<br />
'''Makes base backups''': Yes if the project supports creating binary archives, including the necessary WAL to restore a backed-up instance.<br />
<br />
'''Makes base backups from replicas''': Yes if the project supports creating binary archives and WAL using the PGDATA directory from a replica rather than the master database.<br />
<br />
'''Manages backups''': Yes if the project adds, removes and lists binary archives.<br />
<br />
'''Creates replicas''': Yes if the project automatically adds a recovery.conf (sets up replication) as part of restoring a base backup.<br />
<br />
'''Monitors replication delay''': Yes if the project supports monitoring of replication delay (WAL shipping or streaming replication).<br />
<br />
'''Supports automated failover''': Yes if the project has an option for detecting master failure and promoting a replica to master.<br />
<br />
'''Transport used''': Supported methods for file transfer for making backups or replicas<br />
<br />
= Barman = <br />
<br />
[http://www.pgbarman.org/ pgbarman] [https://github.com/selenamarie/pg_replication_demo/tree/master/barman Demo setup for pgbarman]<br />
<br />
Summary of features: <br />
* Creates base backups<br />
* Uses SSH as transport for backup<br />
* Configuration stored in file or command-line<br />
* Restore is automatable for creating replicas, although not explictly supported<br />
* GPLv3<br />
<br />
Install notes: <br />
* Had a dependency problem with 9.1 on Ubuntu Precise, so installed from source<br />
* Missing dep for argcomplete, noted in README in demo repo<br />
* written in Python<br />
<br />
= OmniPITR = <br />
<br />
[https://github.com/omniti-labs/omnipitr OmniPITR]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/omnipitr Demo of a simple replication setup with OmniPITR]<br />
<br />
Summary of Features:<br />
* Creating PITR backups from Master or Slave<br />
* Restoring a PITR backup for DR<br />
* Creating replicas (by untarring backups)<br />
* Monitoring of replicas<br />
* Supports 'pause removal' of WAL during a backup (nice!)<br />
* PostgreSQL license<br />
<br />
Install notes: <br />
* No packaging, perl <br />
* No documented support for streaming replication<br />
* Uses '^' instead of '%' in custom logfile naming<br />
* No configuration file option (instead of using long command-line options)<br />
* Supported on all Linux, Solaris variants<br />
<br />
= pghoard =<br />
<br />
https://github.com/ohmu/pghoard<br />
<br />
Summary of features:<br />
* Stores basebackups and WAL to cloud object stores (AWS S3, Azure, Ceph, Google Cloud)<br />
* Restore existing basebackups and setup a new cluster with a recovery.conf pointing to another master database<br />
* Create scheduled basebackups<br />
* Can be used as archive_command to archive WALs in the object store<br />
* Can be used as restore_command to restore WALs from the object store<br />
* Basebackup and WAL compression using LZMA<br />
* Optionally encrypts backups<br />
* Supports PITR using timestamps, names and xids<br />
<br />
Install notes:<br />
* Written in Python, includes Debian and Fedora packaging scripts<br />
* 'pghoard' daemon manages basebackups and cleans up WALs<br />
* 'pghoard_archive_command' and 'pghoard_restore' access the locally running 'pghoard' daemon to store and restore files<br />
<br />
= pg-rman =<br />
<br />
[http://code.google.com/p/pg-rman/ pg-rman] [https://github.com/selenamarie/pg_replication_demo/tree/master/pgrman Simple demo for pg_rman setup]<br />
<br />
Summary of features: <br />
* Online backup and recovery, including backup from a replica<br />
* Archive management and restore<br />
* .ini configuration file<br />
* Simple command-line options<br />
<br />
Install notes: <br />
* Written in C, install with 'make USE_PGXS=1'<br />
* On Ubuntu/Debian, installs in non-default bin directory<br />
* Commands are simple, manages WAL archive as well as backups<br />
<br />
<br />
= repmgr =<br />
<br />
[http://www.repmgr.org/ repmgr]<br />
[https://github.com/2ndQuadrant/repmgr GitHub repository]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/repmgr Demo of a simple setup with repmgr]<br />
<br />
Supported features:<br />
* Setting up new replicas/hot_standby with streaming replication (makes recovery.conf itself)<br />
* Making base backups<br />
* Failover (automated, or not, including redirecting replicas to connect to a new master after failover)<br />
* Lag monitoring (repmgrd)<br />
* A "witness" DB server for monitoring (typically on a replica)<br />
* License: GPLv3<br />
<br />
Install notes: <br />
* Written in C<br />
* Developed on Debian systems, so support for package is present. [https://launchpad.net/repmgr Ubuntu packages] are available since Trusty (14.04).<br />
* Otherwise, installs like a typical UNIX utility out of postgresql/contrib source tree (make USE_PGXS=1; make USE_PGXS=1 install)<br />
* Detailed docs are in [https://github.com/2ndQuadrant/repmgr the README] for installing on many Linux platforms<br />
* Doesn't appear to be supported on Mac OS X<br />
<br />
= Skytools / walmgr =<br />
<br />
[https://github.com/markokr/skytools Skytools]<br />
<br />
= WAL-E =<br />
<br />
[https://github.com/wal-e/wal-e WAL-E]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Binary_Replication_Tools&diff=29810Binary Replication Tools2017-04-10T01:33:57Z<p>Dsteele: /* Barman */</p>
<hr />
<div>= Disclaimer =<br />
<br />
This is a Work-In-Progress, started Dec 28, 2012.<br />
<br />
Additions welcome, and [[User:Selena|Selena]] reserves the right to edit. :)<br />
<br />
= Purpose = <br />
<br />
Compare binary replication tools for PostgreSQL for features and ease of use. This document should classify and differentiate binary replication tools for easier selection and fit to purpose.<br />
<br />
== Comparison Matrix ==<br />
<br />
{|border=1<br />
!Tool!!Documentation!!License!!Makes base backups!!Makes base backups from replicas!!Manages backups!!Creates replicas!!Monitors replication delay!!Supports automated failover!!Transport used!!Source includes replication tests<br />
|- style="background-color:#ffffcc;"<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html pg_basebackup]*<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html Postgres docs]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| No<br />
| No<br />
| PostgreSQL connection<br />
|<br />
|-<br />
| [http://www.pgbackrest.org/ pgBackRest] <br />
| [http://www.pgbackrest.org/user-guide.html Documentation]<br />
| MIT<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| ssh<br />
| Yes<br />
<br />
|-<br />
| [http://www.pgbarman.org/ pgbarman] <br />
| [http://docs.pgbarman.org/ Documentation]<br />
| GPLv3<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| Yes<br />
| No<br />
| rsync/ssh, pg_basebackup<br />
|<br />
|-<br />
| [https://github.com/omniti-labs/omnipitr OmniPITR]<br />
| [https://github.com/omniti-labs/omnipitr/blob/master/doc/intro.pod Intro]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| WAL archive delay<br />
| No<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/ohmu/pghoard pghoard]<br />
| [https://github.com/ohmu/pghoard/blob/master/README.rst Readme]<br />
| Apache<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Yes<br />
| No<br />
| No<br />
| AWS S3, Azure, Ceph, Google Cloud Storage<br />
| Yes<br />
|-<br />
| [http://code.google.com/p/pg-rman/ pg-rman] <br />
| [http://code.google.com/p/pg-rman/wiki/readme Readme]<br />
| BSD<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| local / NFS mount<br />
|<br />
|-<br />
| [http://www.repmgr.org/ repmgr]<br />
| [https://github.com/2ndQuadrant/repmgr#readme Readme]<br />
| GPLv3<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| Yes<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/markokr/skytools Skytools]<br />
| [https://github.com/markokr/skytools/blob/master/doc/walmgr3.txt walmgr3]<br />
| BSD-ish<br />
|<br />
|-<br />
| [https://github.com/wal-e/WAL-E WAL-E]<br />
| [https://github.com/wal-e/WAL-E#readme Readme]<br />
| BSD<br />
| Yes<br />
| No<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| HTTPS/SSL<br />
| <br />
|-<br />
|}<br />
<br />
* pg_basebackup is included with a standard PostgreSQL installation.<br />
<br />
<br />
'''Tool''': name of the project that manages binary replication or WAL archiving<br />
<br />
'''Documentation''': Link to canonical documentation for the project. Several projects have broken links that show up as top results in Google.<br />
<br />
'''License''': License software is released under. So far, we only have open/free software projects listed. We could add commercial projects.<br />
<br />
'''Makes base backups''': Yes if the project supports creating binary archives, including the necessary WAL to restore a backed-up instance.<br />
<br />
'''Makes base backups from replicas''': Yes if the project supports creating binary archives and WAL using the PGDATA directory from a replica rather than the master database.<br />
<br />
'''Manages backups''': Yes if the project adds, removes and lists binary archives.<br />
<br />
'''Creates replicas''': Yes if the project automatically adds a recovery.conf (sets up replication) as part of restoring a base backup.<br />
<br />
'''Monitors replication delay''': Yes if the project supports monitoring of replication delay (WAL shipping or streaming replication).<br />
<br />
'''Supports automated failover''': Yes if the project has an option for detecting master failure and promoting a replica to master.<br />
<br />
'''Transport used''': Supported methods for file transfer for making backups or replicas<br />
<br />
= Barman = <br />
<br />
[http://www.pgbarman.org/ pgbarman] [https://github.com/selenamarie/pg_replication_demo/tree/master/barman Demo setup for pgbarman]<br />
<br />
Summary of features: <br />
* Creates base backups<br />
* Uses SSH as transport for backup<br />
* Configuration stored in file or command-line<br />
* Restore is automatable for creating replicas, although not explictly supported<br />
* GPLv3<br />
<br />
Install notes: <br />
* Had a dependency problem with 9.1 on Ubuntu Precise, so installed from source<br />
* Missing dep for argcomplete, noted in README in demo repo<br />
* written in Python<br />
<br />
= pgBackRest =<br />
<br />
[http://www.pgbackrest.org/ pgBackRest]<br />
<br />
Summary of features: <br />
* Parallel Backup & Restore<br />
* Local or Remote Operation<br />
* Full, Incremental, & Differential Backups<br />
* Backup & Archive Expiration<br />
* Backup Resume<br />
* Streaming Compression & Checksums<br />
* Delta Restore<br />
* Parallel WAL Archiving<br />
* Tablespace & Link Support<br />
* Compatibility with PostgreSQL >= 8.3<br />
<br />
= OmniPITR = <br />
<br />
[https://github.com/omniti-labs/omnipitr OmniPITR]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/omnipitr Demo of a simple replication setup with OmniPITR]<br />
<br />
Summary of Features:<br />
* Creating PITR backups from Master or Slave<br />
* Restoring a PITR backup for DR<br />
* Creating replicas (by untarring backups)<br />
* Monitoring of replicas<br />
* Supports 'pause removal' of WAL during a backup (nice!)<br />
* PostgreSQL license<br />
<br />
Install notes: <br />
* No packaging, perl <br />
* No documented support for streaming replication<br />
* Uses '^' instead of '%' in custom logfile naming<br />
* No configuration file option (instead of using long command-line options)<br />
* Supported on all Linux, Solaris variants<br />
<br />
= pghoard =<br />
<br />
https://github.com/ohmu/pghoard<br />
<br />
Summary of features:<br />
* Stores basebackups and WAL to cloud object stores (AWS S3, Azure, Ceph, Google Cloud)<br />
* Restore existing basebackups and setup a new cluster with a recovery.conf pointing to another master database<br />
* Create scheduled basebackups<br />
* Can be used as archive_command to archive WALs in the object store<br />
* Can be used as restore_command to restore WALs from the object store<br />
* Basebackup and WAL compression using LZMA<br />
* Optionally encrypts backups<br />
* Supports PITR using timestamps, names and xids<br />
<br />
Install notes:<br />
* Written in Python, includes Debian and Fedora packaging scripts<br />
* 'pghoard' daemon manages basebackups and cleans up WALs<br />
* 'pghoard_archive_command' and 'pghoard_restore' access the locally running 'pghoard' daemon to store and restore files<br />
<br />
= pg-rman =<br />
<br />
[http://code.google.com/p/pg-rman/ pg-rman] [https://github.com/selenamarie/pg_replication_demo/tree/master/pgrman Simple demo for pg_rman setup]<br />
<br />
Summary of features: <br />
* Online backup and recovery, including backup from a replica<br />
* Archive management and restore<br />
* .ini configuration file<br />
* Simple command-line options<br />
<br />
Install notes: <br />
* Written in C, install with 'make USE_PGXS=1'<br />
* On Ubuntu/Debian, installs in non-default bin directory<br />
* Commands are simple, manages WAL archive as well as backups<br />
<br />
<br />
= repmgr =<br />
<br />
[http://www.repmgr.org/ repmgr]<br />
[https://github.com/2ndQuadrant/repmgr GitHub repository]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/repmgr Demo of a simple setup with repmgr]<br />
<br />
Supported features:<br />
* Setting up new replicas/hot_standby with streaming replication (makes recovery.conf itself)<br />
* Making base backups<br />
* Failover (automated, or not, including redirecting replicas to connect to a new master after failover)<br />
* Lag monitoring (repmgrd)<br />
* A "witness" DB server for monitoring (typically on a replica)<br />
* License: GPLv3<br />
<br />
Install notes: <br />
* Written in C<br />
* Developed on Debian systems, so support for package is present. [https://launchpad.net/repmgr Ubuntu packages] are available since Trusty (14.04).<br />
* Otherwise, installs like a typical UNIX utility out of postgresql/contrib source tree (make USE_PGXS=1; make USE_PGXS=1 install)<br />
* Detailed docs are in [https://github.com/2ndQuadrant/repmgr the README] for installing on many Linux platforms<br />
* Doesn't appear to be supported on Mac OS X<br />
<br />
= Skytools / walmgr =<br />
<br />
[https://github.com/markokr/skytools Skytools]<br />
<br />
= WAL-E =<br />
<br />
[https://github.com/wal-e/wal-e WAL-E]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Binary_Replication_Tools&diff=29808Binary Replication Tools2017-04-10T01:27:31Z<p>Dsteele: /* Comparison Matrix */</p>
<hr />
<div>= Disclaimer =<br />
<br />
This is a Work-In-Progress, started Dec 28, 2012.<br />
<br />
Additions welcome, and [[User:Selena|Selena]] reserves the right to edit. :)<br />
<br />
= Purpose = <br />
<br />
Compare binary replication tools for PostgreSQL for features and ease of use. This document should classify and differentiate binary replication tools for easier selection and fit to purpose.<br />
<br />
== Comparison Matrix ==<br />
<br />
{|border=1<br />
!Tool!!Documentation!!License!!Makes base backups!!Makes base backups from replicas!!Manages backups!!Creates replicas!!Monitors replication delay!!Supports automated failover!!Transport used!!Source includes replication tests<br />
|- style="background-color:#ffffcc;"<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html pg_basebackup]*<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html Postgres docs]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| No<br />
| No<br />
| PostgreSQL connection<br />
|<br />
|-<br />
| [http://www.pgbackrest.org/ pgBackRest] <br />
| [http://www.pgbackrest.org/user-guide.html Documentation]<br />
| MIT<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| ssh<br />
| Yes<br />
<br />
|-<br />
| [http://www.pgbarman.org/ pgbarman] <br />
| [http://docs.pgbarman.org/ Documentation]<br />
| GPLv3<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| Yes<br />
| No<br />
| rsync/ssh, pg_basebackup<br />
|<br />
|-<br />
| [https://github.com/omniti-labs/omnipitr OmniPITR]<br />
| [https://github.com/omniti-labs/omnipitr/blob/master/doc/intro.pod Intro]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| WAL archive delay<br />
| No<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/ohmu/pghoard pghoard]<br />
| [https://github.com/ohmu/pghoard/blob/master/README.rst Readme]<br />
| Apache<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Yes<br />
| No<br />
| No<br />
| AWS S3, Azure, Ceph, Google Cloud Storage<br />
| Yes<br />
|-<br />
| [http://code.google.com/p/pg-rman/ pg-rman] <br />
| [http://code.google.com/p/pg-rman/wiki/readme Readme]<br />
| BSD<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| local / NFS mount<br />
|<br />
|-<br />
| [http://www.repmgr.org/ repmgr]<br />
| [https://github.com/2ndQuadrant/repmgr#readme Readme]<br />
| GPLv3<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| Yes<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/markokr/skytools Skytools]<br />
| [https://github.com/markokr/skytools/blob/master/doc/walmgr3.txt walmgr3]<br />
| BSD-ish<br />
|<br />
|-<br />
| [https://github.com/wal-e/WAL-E WAL-E]<br />
| [https://github.com/wal-e/WAL-E#readme Readme]<br />
| BSD<br />
| Yes<br />
| No<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| HTTPS/SSL<br />
| <br />
|-<br />
|}<br />
<br />
* pg_basebackup is included with a standard PostgreSQL installation.<br />
<br />
<br />
'''Tool''': name of the project that manages binary replication or WAL archiving<br />
<br />
'''Documentation''': Link to canonical documentation for the project. Several projects have broken links that show up as top results in Google.<br />
<br />
'''License''': License software is released under. So far, we only have open/free software projects listed. We could add commercial projects.<br />
<br />
'''Makes base backups''': Yes if the project supports creating binary archives, including the necessary WAL to restore a backed-up instance.<br />
<br />
'''Makes base backups from replicas''': Yes if the project supports creating binary archives and WAL using the PGDATA directory from a replica rather than the master database.<br />
<br />
'''Manages backups''': Yes if the project adds, removes and lists binary archives.<br />
<br />
'''Creates replicas''': Yes if the project automatically adds a recovery.conf (sets up replication) as part of restoring a base backup.<br />
<br />
'''Monitors replication delay''': Yes if the project supports monitoring of replication delay (WAL shipping or streaming replication).<br />
<br />
'''Supports automated failover''': Yes if the project has an option for detecting master failure and promoting a replica to master.<br />
<br />
'''Transport used''': Supported methods for file transfer for making backups or replicas<br />
<br />
= Barman = <br />
<br />
[http://www.pgbarman.org/ pgbarman] [https://github.com/selenamarie/pg_replication_demo/tree/master/barman Demo setup for pgbarman]<br />
<br />
Summary of features: <br />
* Creates base backups<br />
* Uses SSH as transport for backup<br />
* Configuration stored in file or command-line<br />
* Restore is automatable for creating replicas, although not explictly supported<br />
* GPLv3<br />
<br />
Install notes: <br />
* Had a dependency problem with 9.1 on Ubuntu Precise, so installed from source<br />
* Missing dep for argcomplete, noted in README in demo repo<br />
* written in Python<br />
<br />
= OmniPITR = <br />
<br />
[https://github.com/omniti-labs/omnipitr OmniPITR]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/omnipitr Demo of a simple replication setup with OmniPITR]<br />
<br />
Summary of Features:<br />
* Creating PITR backups from Master or Slave<br />
* Restoring a PITR backup for DR<br />
* Creating replicas (by untarring backups)<br />
* Monitoring of replicas<br />
* Supports 'pause removal' of WAL during a backup (nice!)<br />
* PostgreSQL license<br />
<br />
Install notes: <br />
* No packaging, perl <br />
* No documented support for streaming replication<br />
* Uses '^' instead of '%' in custom logfile naming<br />
* No configuration file option (instead of using long command-line options)<br />
* Supported on all Linux, Solaris variants<br />
<br />
= pghoard =<br />
<br />
https://github.com/ohmu/pghoard<br />
<br />
Summary of features:<br />
* Stores basebackups and WAL to cloud object stores (AWS S3, Azure, Ceph, Google Cloud)<br />
* Restore existing basebackups and setup a new cluster with a recovery.conf pointing to another master database<br />
* Create scheduled basebackups<br />
* Can be used as archive_command to archive WALs in the object store<br />
* Can be used as restore_command to restore WALs from the object store<br />
* Basebackup and WAL compression using LZMA<br />
* Optionally encrypts backups<br />
* Supports PITR using timestamps, names and xids<br />
<br />
Install notes:<br />
* Written in Python, includes Debian and Fedora packaging scripts<br />
* 'pghoard' daemon manages basebackups and cleans up WALs<br />
* 'pghoard_archive_command' and 'pghoard_restore' access the locally running 'pghoard' daemon to store and restore files<br />
<br />
= pg-rman =<br />
<br />
[http://code.google.com/p/pg-rman/ pg-rman] [https://github.com/selenamarie/pg_replication_demo/tree/master/pgrman Simple demo for pg_rman setup]<br />
<br />
Summary of features: <br />
* Online backup and recovery, including backup from a replica<br />
* Archive management and restore<br />
* .ini configuration file<br />
* Simple command-line options<br />
<br />
Install notes: <br />
* Written in C, install with 'make USE_PGXS=1'<br />
* On Ubuntu/Debian, installs in non-default bin directory<br />
* Commands are simple, manages WAL archive as well as backups<br />
<br />
<br />
= repmgr =<br />
<br />
[http://www.repmgr.org/ repmgr]<br />
[https://github.com/2ndQuadrant/repmgr GitHub repository]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/repmgr Demo of a simple setup with repmgr]<br />
<br />
Supported features:<br />
* Setting up new replicas/hot_standby with streaming replication (makes recovery.conf itself)<br />
* Making base backups<br />
* Failover (automated, or not, including redirecting replicas to connect to a new master after failover)<br />
* Lag monitoring (repmgrd)<br />
* A "witness" DB server for monitoring (typically on a replica)<br />
* License: GPLv3<br />
<br />
Install notes: <br />
* Written in C<br />
* Developed on Debian systems, so support for package is present. [https://launchpad.net/repmgr Ubuntu packages] are available since Trusty (14.04).<br />
* Otherwise, installs like a typical UNIX utility out of postgresql/contrib source tree (make USE_PGXS=1; make USE_PGXS=1 install)<br />
* Detailed docs are in [https://github.com/2ndQuadrant/repmgr the README] for installing on many Linux platforms<br />
* Doesn't appear to be supported on Mac OS X<br />
<br />
= Skytools / walmgr =<br />
<br />
[https://github.com/markokr/skytools Skytools]<br />
<br />
= WAL-E =<br />
<br />
[https://github.com/wal-e/wal-e WAL-E]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Binary_Replication_Tools&diff=29807Binary Replication Tools2017-04-10T01:27:13Z<p>Dsteele: /* Comparison Matrix */</p>
<hr />
<div>= Disclaimer =<br />
<br />
This is a Work-In-Progress, started Dec 28, 2012.<br />
<br />
Additions welcome, and [[User:Selena|Selena]] reserves the right to edit. :)<br />
<br />
= Purpose = <br />
<br />
Compare binary replication tools for PostgreSQL for features and ease of use. This document should classify and differentiate binary replication tools for easier selection and fit to purpose.<br />
<br />
== Comparison Matrix ==<br />
<br />
{|border=1<br />
!Tool!!Documentation!!License!!Makes base backups!!Makes base backups from replicas!!Manages backups!!Creates replicas!!Monitors replication delay!!Supports automated failover!!Transport used!!Source includes replication tests<br />
|- style="background-color:#ffffcc;"<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html pg_basebackup]*<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html Postgres docs]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| No<br />
| No<br />
| PostgreSQL connection<br />
|<br />
|-<br />
| [http://www.pgbackrest.org/ pgBackRest] <br />
| [http://www.pgbackrest.org/user-guide.html Documentation]<br />
| MIT<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| ssh<br />
Yes<br />
<br />
|-<br />
| [http://www.pgbarman.org/ pgbarman] <br />
| [http://docs.pgbarman.org/ Documentation]<br />
| GPLv3<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| Yes<br />
| No<br />
| rsync/ssh, pg_basebackup<br />
|<br />
|-<br />
| [https://github.com/omniti-labs/omnipitr OmniPITR]<br />
| [https://github.com/omniti-labs/omnipitr/blob/master/doc/intro.pod Intro]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| WAL archive delay<br />
| No<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/ohmu/pghoard pghoard]<br />
| [https://github.com/ohmu/pghoard/blob/master/README.rst Readme]<br />
| Apache<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Yes<br />
| No<br />
| No<br />
| AWS S3, Azure, Ceph, Google Cloud Storage<br />
| Yes<br />
|-<br />
| [http://code.google.com/p/pg-rman/ pg-rman] <br />
| [http://code.google.com/p/pg-rman/wiki/readme Readme]<br />
| BSD<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| local / NFS mount<br />
|<br />
|-<br />
| [http://www.repmgr.org/ repmgr]<br />
| [https://github.com/2ndQuadrant/repmgr#readme Readme]<br />
| GPLv3<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| Yes<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/markokr/skytools Skytools]<br />
| [https://github.com/markokr/skytools/blob/master/doc/walmgr3.txt walmgr3]<br />
| BSD-ish<br />
|<br />
|-<br />
| [https://github.com/wal-e/WAL-E WAL-E]<br />
| [https://github.com/wal-e/WAL-E#readme Readme]<br />
| BSD<br />
| Yes<br />
| No<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| HTTPS/SSL<br />
| <br />
|-<br />
|}<br />
<br />
* pg_basebackup is included with a standard PostgreSQL installation.<br />
<br />
<br />
'''Tool''': name of the project that manages binary replication or WAL archiving<br />
<br />
'''Documentation''': Link to canonical documentation for the project. Several projects have broken links that show up as top results in Google.<br />
<br />
'''License''': License software is released under. So far, we only have open/free software projects listed. We could add commercial projects.<br />
<br />
'''Makes base backups''': Yes if the project supports creating binary archives, including the necessary WAL to restore a backed-up instance.<br />
<br />
'''Makes base backups from replicas''': Yes if the project supports creating binary archives and WAL using the PGDATA directory from a replica rather than the master database.<br />
<br />
'''Manages backups''': Yes if the project adds, removes and lists binary archives.<br />
<br />
'''Creates replicas''': Yes if the project automatically adds a recovery.conf (sets up replication) as part of restoring a base backup.<br />
<br />
'''Monitors replication delay''': Yes if the project supports monitoring of replication delay (WAL shipping or streaming replication).<br />
<br />
'''Supports automated failover''': Yes if the project has an option for detecting master failure and promoting a replica to master.<br />
<br />
'''Transport used''': Supported methods for file transfer for making backups or replicas<br />
<br />
= Barman = <br />
<br />
[http://www.pgbarman.org/ pgbarman] [https://github.com/selenamarie/pg_replication_demo/tree/master/barman Demo setup for pgbarman]<br />
<br />
Summary of features: <br />
* Creates base backups<br />
* Uses SSH as transport for backup<br />
* Configuration stored in file or command-line<br />
* Restore is automatable for creating replicas, although not explictly supported<br />
* GPLv3<br />
<br />
Install notes: <br />
* Had a dependency problem with 9.1 on Ubuntu Precise, so installed from source<br />
* Missing dep for argcomplete, noted in README in demo repo<br />
* written in Python<br />
<br />
= OmniPITR = <br />
<br />
[https://github.com/omniti-labs/omnipitr OmniPITR]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/omnipitr Demo of a simple replication setup with OmniPITR]<br />
<br />
Summary of Features:<br />
* Creating PITR backups from Master or Slave<br />
* Restoring a PITR backup for DR<br />
* Creating replicas (by untarring backups)<br />
* Monitoring of replicas<br />
* Supports 'pause removal' of WAL during a backup (nice!)<br />
* PostgreSQL license<br />
<br />
Install notes: <br />
* No packaging, perl <br />
* No documented support for streaming replication<br />
* Uses '^' instead of '%' in custom logfile naming<br />
* No configuration file option (instead of using long command-line options)<br />
* Supported on all Linux, Solaris variants<br />
<br />
= pghoard =<br />
<br />
https://github.com/ohmu/pghoard<br />
<br />
Summary of features:<br />
* Stores basebackups and WAL to cloud object stores (AWS S3, Azure, Ceph, Google Cloud)<br />
* Restore existing basebackups and setup a new cluster with a recovery.conf pointing to another master database<br />
* Create scheduled basebackups<br />
* Can be used as archive_command to archive WALs in the object store<br />
* Can be used as restore_command to restore WALs from the object store<br />
* Basebackup and WAL compression using LZMA<br />
* Optionally encrypts backups<br />
* Supports PITR using timestamps, names and xids<br />
<br />
Install notes:<br />
* Written in Python, includes Debian and Fedora packaging scripts<br />
* 'pghoard' daemon manages basebackups and cleans up WALs<br />
* 'pghoard_archive_command' and 'pghoard_restore' access the locally running 'pghoard' daemon to store and restore files<br />
<br />
= pg-rman =<br />
<br />
[http://code.google.com/p/pg-rman/ pg-rman] [https://github.com/selenamarie/pg_replication_demo/tree/master/pgrman Simple demo for pg_rman setup]<br />
<br />
Summary of features: <br />
* Online backup and recovery, including backup from a replica<br />
* Archive management and restore<br />
* .ini configuration file<br />
* Simple command-line options<br />
<br />
Install notes: <br />
* Written in C, install with 'make USE_PGXS=1'<br />
* On Ubuntu/Debian, installs in non-default bin directory<br />
* Commands are simple, manages WAL archive as well as backups<br />
<br />
<br />
= repmgr =<br />
<br />
[http://www.repmgr.org/ repmgr]<br />
[https://github.com/2ndQuadrant/repmgr GitHub repository]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/repmgr Demo of a simple setup with repmgr]<br />
<br />
Supported features:<br />
* Setting up new replicas/hot_standby with streaming replication (makes recovery.conf itself)<br />
* Making base backups<br />
* Failover (automated, or not, including redirecting replicas to connect to a new master after failover)<br />
* Lag monitoring (repmgrd)<br />
* A "witness" DB server for monitoring (typically on a replica)<br />
* License: GPLv3<br />
<br />
Install notes: <br />
* Written in C<br />
* Developed on Debian systems, so support for package is present. [https://launchpad.net/repmgr Ubuntu packages] are available since Trusty (14.04).<br />
* Otherwise, installs like a typical UNIX utility out of postgresql/contrib source tree (make USE_PGXS=1; make USE_PGXS=1 install)<br />
* Detailed docs are in [https://github.com/2ndQuadrant/repmgr the README] for installing on many Linux platforms<br />
* Doesn't appear to be supported on Mac OS X<br />
<br />
= Skytools / walmgr =<br />
<br />
[https://github.com/markokr/skytools Skytools]<br />
<br />
= WAL-E =<br />
<br />
[https://github.com/wal-e/wal-e WAL-E]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Binary_Replication_Tools&diff=29806Binary Replication Tools2017-04-10T00:53:17Z<p>Dsteele: /* Comparison Matrix */</p>
<hr />
<div>= Disclaimer =<br />
<br />
This is a Work-In-Progress, started Dec 28, 2012.<br />
<br />
Additions welcome, and [[User:Selena|Selena]] reserves the right to edit. :)<br />
<br />
= Purpose = <br />
<br />
Compare binary replication tools for PostgreSQL for features and ease of use. This document should classify and differentiate binary replication tools for easier selection and fit to purpose.<br />
<br />
== Comparison Matrix ==<br />
<br />
{|border=1<br />
!Tool!!Documentation!!License!!Makes base backups!!Makes base backups from replicas!!Manages backups!!Creates replicas!!Monitors replication delay!!Supports automated failover!!Transport used!!Source includes replication tests<br />
|- style="background-color:#ffffcc;"<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html pg_basebackup]*<br />
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html Postgres docs]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| No<br />
| No<br />
| PostgreSQL connection<br />
|<br />
|-<br />
| [http://www.pgbackrest.org/ pgBackRest] <br />
| [http://www.pgbackrest.org/user-guide.html Documentation]<br />
| MIT<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| <br />
| No<br />
| ssh<br />
<br />
|-<br />
| [http://www.pgbarman.org/ pgbarman] <br />
| [http://docs.pgbarman.org/ Documentation]<br />
| GPLv3<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| Yes<br />
| No<br />
| rsync/ssh, pg_basebackup<br />
|<br />
|-<br />
| [https://github.com/omniti-labs/omnipitr OmniPITR]<br />
| [https://github.com/omniti-labs/omnipitr/blob/master/doc/intro.pod Intro]<br />
| PostgreSQL<br />
| Yes<br />
| Yes<br />
| No<br />
| Manual<br />
| WAL archive delay<br />
| No<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/ohmu/pghoard pghoard]<br />
| [https://github.com/ohmu/pghoard/blob/master/README.rst Readme]<br />
| Apache<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Yes<br />
| No<br />
| No<br />
| AWS S3, Azure, Ceph, Google Cloud Storage<br />
| Yes<br />
|-<br />
| [http://code.google.com/p/pg-rman/ pg-rman] <br />
| [http://code.google.com/p/pg-rman/wiki/readme Readme]<br />
| BSD<br />
| Yes<br />
| Yes<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| local / NFS mount<br />
|<br />
|-<br />
| [http://www.repmgr.org/ repmgr]<br />
| [https://github.com/2ndQuadrant/repmgr#readme Readme]<br />
| GPLv3<br />
| No<br />
| No<br />
| No<br />
| Yes<br />
| Yes<br />
| Yes<br />
| rsync / ssh<br />
|<br />
|-<br />
| [https://github.com/markokr/skytools Skytools]<br />
| [https://github.com/markokr/skytools/blob/master/doc/walmgr3.txt walmgr3]<br />
| BSD-ish<br />
|<br />
|-<br />
| [https://github.com/wal-e/WAL-E WAL-E]<br />
| [https://github.com/wal-e/WAL-E#readme Readme]<br />
| BSD<br />
| Yes<br />
| No<br />
| Yes<br />
| Manual<br />
| No<br />
| No<br />
| HTTPS/SSL<br />
| <br />
|-<br />
|}<br />
<br />
* pg_basebackup is included with a standard PostgreSQL installation.<br />
<br />
<br />
'''Tool''': name of the project that manages binary replication or WAL archiving<br />
<br />
'''Documentation''': Link to canonical documentation for the project. Several projects have broken links that show up as top results in Google.<br />
<br />
'''License''': License software is released under. So far, we only have open/free software projects listed. We could add commercial projects.<br />
<br />
'''Makes base backups''': Yes if the project supports creating binary archives, including the necessary WAL to restore a backed-up instance.<br />
<br />
'''Makes base backups from replicas''': Yes if the project supports creating binary archives and WAL using the PGDATA directory from a replica rather than the master database.<br />
<br />
'''Manages backups''': Yes if the project adds, removes and lists binary archives.<br />
<br />
'''Creates replicas''': Yes if the project automatically adds a recovery.conf (sets up replication) as part of restoring a base backup.<br />
<br />
'''Monitors replication delay''': Yes if the project supports monitoring of replication delay (WAL shipping or streaming replication).<br />
<br />
'''Supports automated failover''': Yes if the project has an option for detecting master failure and promoting a replica to master.<br />
<br />
'''Transport used''': Supported methods for file transfer for making backups or replicas<br />
<br />
= Barman = <br />
<br />
[http://www.pgbarman.org/ pgbarman] [https://github.com/selenamarie/pg_replication_demo/tree/master/barman Demo setup for pgbarman]<br />
<br />
Summary of features: <br />
* Creates base backups<br />
* Uses SSH as transport for backup<br />
* Configuration stored in file or command-line<br />
* Restore is automatable for creating replicas, although not explictly supported<br />
* GPLv3<br />
<br />
Install notes: <br />
* Had a dependency problem with 9.1 on Ubuntu Precise, so installed from source<br />
* Missing dep for argcomplete, noted in README in demo repo<br />
* written in Python<br />
<br />
= OmniPITR = <br />
<br />
[https://github.com/omniti-labs/omnipitr OmniPITR]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/omnipitr Demo of a simple replication setup with OmniPITR]<br />
<br />
Summary of Features:<br />
* Creating PITR backups from Master or Slave<br />
* Restoring a PITR backup for DR<br />
* Creating replicas (by untarring backups)<br />
* Monitoring of replicas<br />
* Supports 'pause removal' of WAL during a backup (nice!)<br />
* PostgreSQL license<br />
<br />
Install notes: <br />
* No packaging, perl <br />
* No documented support for streaming replication<br />
* Uses '^' instead of '%' in custom logfile naming<br />
* No configuration file option (instead of using long command-line options)<br />
* Supported on all Linux, Solaris variants<br />
<br />
= pghoard =<br />
<br />
https://github.com/ohmu/pghoard<br />
<br />
Summary of features:<br />
* Stores basebackups and WAL to cloud object stores (AWS S3, Azure, Ceph, Google Cloud)<br />
* Restore existing basebackups and setup a new cluster with a recovery.conf pointing to another master database<br />
* Create scheduled basebackups<br />
* Can be used as archive_command to archive WALs in the object store<br />
* Can be used as restore_command to restore WALs from the object store<br />
* Basebackup and WAL compression using LZMA<br />
* Optionally encrypts backups<br />
* Supports PITR using timestamps, names and xids<br />
<br />
Install notes:<br />
* Written in Python, includes Debian and Fedora packaging scripts<br />
* 'pghoard' daemon manages basebackups and cleans up WALs<br />
* 'pghoard_archive_command' and 'pghoard_restore' access the locally running 'pghoard' daemon to store and restore files<br />
<br />
= pg-rman =<br />
<br />
[http://code.google.com/p/pg-rman/ pg-rman] [https://github.com/selenamarie/pg_replication_demo/tree/master/pgrman Simple demo for pg_rman setup]<br />
<br />
Summary of features: <br />
* Online backup and recovery, including backup from a replica<br />
* Archive management and restore<br />
* .ini configuration file<br />
* Simple command-line options<br />
<br />
Install notes: <br />
* Written in C, install with 'make USE_PGXS=1'<br />
* On Ubuntu/Debian, installs in non-default bin directory<br />
* Commands are simple, manages WAL archive as well as backups<br />
<br />
<br />
= repmgr =<br />
<br />
[http://www.repmgr.org/ repmgr]<br />
[https://github.com/2ndQuadrant/repmgr GitHub repository]<br />
[https://github.com/selenamarie/pg_replication_demo/tree/master/repmgr Demo of a simple setup with repmgr]<br />
<br />
Supported features:<br />
* Setting up new replicas/hot_standby with streaming replication (makes recovery.conf itself)<br />
* Making base backups<br />
* Failover (automated, or not, including redirecting replicas to connect to a new master after failover)<br />
* Lag monitoring (repmgrd)<br />
* A "witness" DB server for monitoring (typically on a replica)<br />
* License: GPLv3<br />
<br />
Install notes: <br />
* Written in C<br />
* Developed on Debian systems, so support for package is present. [https://launchpad.net/repmgr Ubuntu packages] are available since Trusty (14.04).<br />
* Otherwise, installs like a typical UNIX utility out of postgresql/contrib source tree (make USE_PGXS=1; make USE_PGXS=1 install)<br />
* Detailed docs are in [https://github.com/2ndQuadrant/repmgr the README] for installing on many Linux platforms<br />
* Doesn't appear to be supported on Mac OS X<br />
<br />
= Skytools / walmgr =<br />
<br />
[https://github.com/markokr/skytools Skytools]<br />
<br />
= WAL-E =<br />
<br />
[https://github.com/wal-e/wal-e WAL-E]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PgConfUS_Talks_2017&diff=29709PgConfUS Talks 20172017-03-31T20:23:47Z<p>Dsteele: /* Liberty II */</p>
<hr />
<div>= PGConf US 2017 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://www.pgconf.us/2017/<br />
<br />
== Videos ==<br />
<br />
https://www.youtube.com/pgconfus/<br />
<br />
== Trainings: Tuesday, 28 March 2017 ==<br />
* PostgreSQL When It's Not Your Job, Christophe Pettus<br />
* Designing a Multi-tenant Database for Scale with PostgreSQL, Ozgun Erdogan and Lukas Fittl<br />
* Pacific Crest Trail: The postgresql.conf from A-Z, Joshua D. Drake<br />
* Detecting performance problems and fixing them, Hans-Jürgen Schönig<br />
* Getting Stuff done with PostGIS, Leo Hsu and Regina Obe<br />
* Linux IO internals for PostgreSQL administrators, Ilya Kosmodemiansky<br />
<br />
== Regulated Industry Summit ==<br />
* Creating blockchain platforms and future directions, Ryan Smith<br />
* Blockchain, Distributed Security and Regulated Industries, Chris Dannen<br />
* Public Clouds & Risk Assessments for Regulated Industries, Kai Huang<br />
* Secure Containers, Bridging Mainframes to Cloud, (IBM), Diana Henderson<br />
* Engineering cloud infrastructure for HIPAA-compliance, Shaun Qualheim<br />
* HIPAA Compliant, Scalable and Highly Available PostgreSQL Architecture in AWS, Yaser Raja and Glenn Poston<br />
* How to Make Security on NoSQL More than just an afterthought, Chad Hardin<br />
* Secure Technical Implementation Guide (STIG) For PostgreSQL, Jason O'Donnell<br />
* Security Enhancements in Postgres 10, Simon Riggs<br />
<br />
== Sessions: Wednesday, 29 March 2017 ==<br />
<br />
=== Liberty I ===<br />
* [https://www.joeconway.com/presentations/intro_to_postgresql-pgconf.us-2017.pdf Intro to PostgreSQL - a jumpstart to up and running], Joe Conway<br />
<br />
=== Liberty II ===<br />
<br />
=== Liberty III ===<br />
<br />
=== America ===<br />
* [http://www.slideshare.net/PostgreSQL-Consulting/postgresql-worst-practices-version-pgconfus-2017-by-ilya-kosmodemiansky PostgreSQL worst practices], Ilya Kosmodemiansky<br />
<br />
== Sessions: Thursday, 30 March 2017 ==<br />
<br />
=== Liberty I ===<br />
<br />
=== Liberty II ===<br />
* [https://github.com/dwsteele/conference/blob/release/AuditLogging-PGConfUS-2017/slides.pdf Audit Logging for PostgreSQL], David Steele<br />
<br />
=== Liberty III ===<br />
<br />
=== America ===<br />
<br />
== Sessions:Friday, 31 March 2017 ==<br />
<br />
=== Liberty I ===<br />
<br />
=== Liberty II ===<br />
* [https://www.joeconway.com/presentations/plr-spatial-pgconf.us-2017.pdf How Green Was My Valley - Spatial Analytics], Joe Conway<br />
<br />
=== Liberty III ===<br />
<br />
=== America ===</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2016&diff=28547PostgreSQL Conference Europe Talks 20162016-11-04T16:48:07Z<p>Dsteele: /* Friday */</p>
<hr />
<div>pgconf.eu 2016 took place in Tallinn, Estonia, from 2016-11-01 to 2016-11-04.<br />
<br />
== Tuesday (Trainings) ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Trainer||Title (Link to slides)<br />
|+<br />
| 09:00 - 17:00 || Alfa 2 || Petr Jelinek, Simon Riggs || PostgreSQL Replication & Upgrades<br />
|}<br />
<br />
== Wednesday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 11:10 - 12:00 || Alpha 2 || David Steele || [https://github.com/dwsteele/conference/blob/release/PostgresPatchReview-PGConfEU-2016/slides/slides.pdf Reviewing PostgreSQL Patches for Fun and Profit]<br />
|-<br />
| 14:00 - 14:50 || Omega || Alexander Korotkov || [http://www.slideshare.net/AlexanderKorotkov/the-future-is-csn The future is CSN]<br />
|-<br />
| 16:20 - 17:10 || Alpha 2 || Jehan-Guillaume (ioguix) de Rorthais || [http://www.dalibo.org/_media/2016-pgconfeu-paf.html.gz PAF: auto failover and more!]<br />
|}<br />
<br />
== Thursday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 11:50 - 12:40 || Alpha 2 || Alexey Lesovsky || [http://www.slideshare.net/alexeylesovsky/manage-postgresql-with-pgcenter Managing PostgreSQL with pgCenter]<br />
|+<br />
| 15:40 - 16:30 || Alpha 2 || Cédric Villemain || Transactions across multiple datastores<br />
|}<br />
<br />
== Friday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 11:50 - 12:40 || Alpha 1 || David Steele || [https://github.com/dwsteele/conference/blob/release/AuditLogging-PGConfEU-2016/slides.pdf Audit Logging for PostgreSQL]<br />
|-<br />
| 13:40 - 14:30 || Omega || Cédric Villemain || A close look at stats: what you can do with them !<br />
|}</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2016&diff=28546PostgreSQL Conference Europe Talks 20162016-11-04T16:44:15Z<p>Dsteele: /* Wednesday */</p>
<hr />
<div>pgconf.eu 2016 took place in Tallinn, Estonia, from 2016-11-01 to 2016-11-04.<br />
<br />
== Tuesday (Trainings) ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Trainer||Title (Link to slides)<br />
|+<br />
| 09:00 - 17:00 || Alfa 2 || Petr Jelinek, Simon Riggs || PostgreSQL Replication & Upgrades<br />
|}<br />
<br />
== Wednesday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 11:10 - 12:00 || Alpha 2 || David Steele || [https://github.com/dwsteele/conference/blob/release/PostgresPatchReview-PGConfEU-2016/slides/slides.pdf Reviewing PostgreSQL Patches for Fun and Profit]<br />
|-<br />
| 14:00 - 14:50 || Omega || Alexander Korotkov || [http://www.slideshare.net/AlexanderKorotkov/the-future-is-csn The future is CSN]<br />
|-<br />
| 16:20 - 17:10 || Alpha 2 || Jehan-Guillaume (ioguix) de Rorthais || [http://www.dalibo.org/_media/2016-pgconfeu-paf.html.gz PAF: auto failover and more!]<br />
|}<br />
<br />
== Thursday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 11:50 - 12:40 || Alpha 2 || Alexey Lesovsky || [http://www.slideshare.net/alexeylesovsky/manage-postgresql-with-pgcenter Managing PostgreSQL with pgCenter]<br />
|+<br />
| 15:40 - 16:30 || Alpha 2 || Cédric Villemain || Transactions across multiple datastores<br />
|}<br />
<br />
== Friday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 13:40 - 14:30 || Omega || Cédric Villemain || A close look at stats: what you can do with them !<br />
|}</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2016&diff=28545PostgreSQL Conference Europe Talks 20162016-11-04T16:43:51Z<p>Dsteele: /* Wednesday */</p>
<hr />
<div>pgconf.eu 2016 took place in Tallinn, Estonia, from 2016-11-01 to 2016-11-04.<br />
<br />
== Tuesday (Trainings) ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Trainer||Title (Link to slides)<br />
|+<br />
| 09:00 - 17:00 || Alfa 2 || Petr Jelinek, Simon Riggs || PostgreSQL Replication & Upgrades<br />
|}<br />
<br />
== Wednesday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 11:10 - 12:00 || Alpha 2 || David Steele || [https://github.com/dwsteele/conference/blob/release/PostgresPatchReview-PGConfEU-2016/slides/slides.pdf Reviewing PostgreSQL Patches for Fun and Profit]<br />
| 14:00 - 14:50 || Omega || Alexander Korotkov || [http://www.slideshare.net/AlexanderKorotkov/the-future-is-csn The future is CSN]<br />
|-<br />
| 16:20 - 17:10 || Alpha 2 || Jehan-Guillaume (ioguix) de Rorthais || [http://www.dalibo.org/_media/2016-pgconfeu-paf.html.gz PAF: auto failover and more!]<br />
|}<br />
<br />
== Thursday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 11:50 - 12:40 || Alpha 2 || Alexey Lesovsky || [http://www.slideshare.net/alexeylesovsky/manage-postgresql-with-pgcenter Managing PostgreSQL with pgCenter]<br />
|+<br />
| 15:40 - 16:30 || Alpha 2 || Cédric Villemain || Transactions across multiple datastores<br />
|}<br />
<br />
== Friday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 13:40 - 14:30 || Omega || Cédric Villemain || A close look at stats: what you can do with them !<br />
|}</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Postgres_Open_2016&diff=28229Postgres Open 20162016-09-16T15:06:06Z<p>Dsteele: /* Wednesday September 14 */</p>
<hr />
<div>Conference website: [http://2016.postgresopen.org/ PostgresOpen 2016]<br />
<br />
[https://postgresopen.org/events/feedback/pgopen2016/ Conference Feedback]<br />
<br />
Events shown for placeholding purposes. See the "Editing help" for instructions on how to add a link to your slides.<br />
<br />
== Tuesday September 13 (Tutorials) ==<br />
* Introduction to PostGIS (Regina Obe and Leo Hsu)<br />
* Seamless failover with pgBouncer and Consul (Scott Mead)<br />
* Linux tuning to improve PostgreSQL performance: from hardware to postgresql.conf (Ilya Kosmodemiansky)<br />
* Advanced SQL + Functions (Joe Conway, Stephen Frost)<br />
* Autoscaling PostgreSQL with Kubernetes and OpenShift Part 1 (Jeff McCormick, Steven Pousty)<br />
<br />
== Wednesday September 14 ==<br />
* Digital Service Expert at the United States Digital Service, @USDS keynote (Marianne Bellotti)<br />
<br />
* A Look at the Elephant's Tail (Greg Stark)<br />
* A look at the Elephants trunk - PostgreSQL 9.6 (Magnus Hagander)<br />
* Flexible Indexing with Postgres (Bruce Momjian)<br />
* CREATE INDEX ... USING RUM. RUM index and its applications to FTS. (Oleg Bartunov)<br />
* Locked Up: Advances in Postgres Data Encryption (Vibhor Kumar)<br />
* [http://www.pgbackrest.org/media/slide/pgBackRest-PostgresOpen-2016.pdf Efficiently Backing up Terabytes of Data with pgBackRest] (David Steele)<br />
* [http://www.slideshare.net/SeanChittenden/dynamic-database-credentials-security-contingency-planning Assume database credentials have leaked: Dynamic Database credentials...] (Sean Chittenden) ([https://github.com/sean-/pgopen16-dyn-creds GitHub demo material])<br />
* You'd better have tested backups... (Dimitri Fontaine)<br />
* The Elephant Meets the Whale - Bringing PostgreSQL to Production on Docker (Phil Vacca)<br />
* [https://github.com/dwsteele/conference/blob/release/PostgresPatchReview-PostgresOpen-2016/slides/slides.pdf Reviewing PostgreSQL Patches for Fun and Profit] (David Steele)<br />
* Does Anybody Really Know What Time It Is? (Michael Alan Brewer)<br />
* PGLogical - the logical replication for PostgreSQL (Petr Jelinek)<br />
* Shall We Play a Game? (with CTEs) (James Coleman)<br />
* Performance Improvements in PostgreSQL 9.5, 9.6 and beyond (Tomas Vondra)<br />
* All the Big Data Sciency stuff you never knew Postgres could do (Jim Nasby)<br />
* Using PostGIS to Handle Geospatial Data as Vectors and Rasters (Dylan Herron)<br />
<br />
== Lightning Talks ==<br />
* [https://www.slideshare.net/SeanChittenden/postgres-on-zfs-lightning-talk PostgreSQL on ZFS], Sean Chittenden<br />
<br />
== Thursday, September 15 ==<br />
<br />
* [http://www.pateldenish.com/2016/09/advanced-postgres-monitoring.html Advanced Postgres Monitoring] (Denish Patel)<br />
* An opinionated guide to PostgreSQL replication (Peter Eisentraut)<br />
* Amazon RDS for PostgreSQL: New Features and Lessons Learned (Grant McAlister)<br />
* PostgreSQL Backups the modern ways (Magnus Hagander)<br />
* Big Data with PostgreSQL (Simon Riggs)<br />
* PostgreSQL worst practices (Ilya Kosmodemiansky)<br />
* Using PostgreSQL in a Small Business (Preston Hagar)<br />
* Administering Postgres using Docker and Openshift (Jeff McCormick)<br />
* Permissions in Postgres (Nathan Wagner)<br />
* Elephant Herd as a Service: Managing Hundreds of Postgres Instances (Shaun Thomas)<br />
* Managing OS Provided PostgreSQL Packages (Keith Fiske)<br />
* Data Architecture with PostgreSQL (Kevin Kempter)<br />
* Bitemporal Data Model: making it happened in Postgres (Henrietta Dombrovskaya)<br />
* [http://anarazel.de/talks/pgopen-dallas-2016-09-15/durability.pdf Understanding Durability in Postgres] (Andres Freund)<br />
* PostgreSQL with Chef & Puppet (Scott Mead)<br />
* Data Analysis with PL/Python (Keith Robertson)<br />
* JDBC performance from the inside (Dave Cramer)<br />
* Growing with your Data (Richard Silva)</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Postgres_Open_2016&diff=28228Postgres Open 20162016-09-16T15:04:34Z<p>Dsteele: /* Wednesday September 14 */</p>
<hr />
<div>Conference website: [http://2016.postgresopen.org/ PostgresOpen 2016]<br />
<br />
[https://postgresopen.org/events/feedback/pgopen2016/ Conference Feedback]<br />
<br />
Events shown for placeholding purposes. See the "Editing help" for instructions on how to add a link to your slides.<br />
<br />
== Tuesday September 13 (Tutorials) ==<br />
* Introduction to PostGIS (Regina Obe and Leo Hsu)<br />
* Seamless failover with pgBouncer and Consul (Scott Mead)<br />
* Linux tuning to improve PostgreSQL performance: from hardware to postgresql.conf (Ilya Kosmodemiansky)<br />
* Advanced SQL + Functions (Joe Conway, Stephen Frost)<br />
* Autoscaling PostgreSQL with Kubernetes and OpenShift Part 1 (Jeff McCormick, Steven Pousty)<br />
<br />
== Wednesday September 14 ==<br />
* Digital Service Expert at the United States Digital Service, @USDS keynote (Marianne Bellotti)<br />
<br />
* A Look at the Elephant's Tail (Greg Stark)<br />
* A look at the Elephants trunk - PostgreSQL 9.6 (Magnus Hagander)<br />
* Flexible Indexing with Postgres (Bruce Momjian)<br />
* CREATE INDEX ... USING RUM. RUM index and its applications to FTS. (Oleg Bartunov)<br />
* Locked Up: Advances in Postgres Data Encryption (Vibhor Kumar)<br />
* Efficiently Backing up Terabytes of Data with pgBackRest (David Steele) [http://www.pgbackrest.org/media/slide/pgBackRest-PostgresOpen-2016.pdf]<br />
* [http://www.slideshare.net/SeanChittenden/dynamic-database-credentials-security-contingency-planning Assume database credentials have leaked: Dynamic Database credentials...] (Sean Chittenden) ([https://github.com/sean-/pgopen16-dyn-creds GitHub demo material])<br />
* You'd better have tested backups... (Dimitri Fontaine)<br />
* The Elephant Meets the Whale - Bringing PostgreSQL to Production on Docker (Phil Vacca)<br />
* Reviewing PostgreSQL Patches for Fun and Profit (David Steele) [https://github.com/dwsteele/conference/blob/release/PostgresPatchReview-PostgresOpen-2016/slides/slides.pdf]<br />
* Does Anybody Really Know What Time It Is? (Michael Alan Brewer)<br />
* PGLogical - the logical replication for PostgreSQL (Petr Jelinek)<br />
* Shall We Play a Game? (with CTEs) (James Coleman)<br />
* Performance Improvements in PostgreSQL 9.5, 9.6 and beyond (Tomas Vondra)<br />
* All the Big Data Sciency stuff you never knew Postgres could do (Jim Nasby)<br />
* Using PostGIS to Handle Geospatial Data as Vectors and Rasters (Dylan Herron)<br />
<br />
== Lightning Talks ==<br />
* [https://www.slideshare.net/SeanChittenden/postgres-on-zfs-lightning-talk PostgreSQL on ZFS], Sean Chittenden<br />
<br />
== Thursday, September 15 ==<br />
<br />
* [http://www.pateldenish.com/2016/09/advanced-postgres-monitoring.html Advanced Postgres Monitoring] (Denish Patel)<br />
* An opinionated guide to PostgreSQL replication (Peter Eisentraut)<br />
* Amazon RDS for PostgreSQL: New Features and Lessons Learned (Grant McAlister)<br />
* PostgreSQL Backups the modern ways (Magnus Hagander)<br />
* Big Data with PostgreSQL (Simon Riggs)<br />
* PostgreSQL worst practices (Ilya Kosmodemiansky)<br />
* Using PostgreSQL in a Small Business (Preston Hagar)<br />
* Administering Postgres using Docker and Openshift (Jeff McCormick)<br />
* Permissions in Postgres (Nathan Wagner)<br />
* Elephant Herd as a Service: Managing Hundreds of Postgres Instances (Shaun Thomas)<br />
* Managing OS Provided PostgreSQL Packages (Keith Fiske)<br />
* Data Architecture with PostgreSQL (Kevin Kempter)<br />
* Bitemporal Data Model: making it happened in Postgres (Henrietta Dombrovskaya)<br />
* [http://anarazel.de/talks/pgopen-dallas-2016-09-15/durability.pdf Understanding Durability in Postgres] (Andres Freund)<br />
* PostgreSQL with Chef & Puppet (Scott Mead)<br />
* Data Analysis with PL/Python (Keith Robertson)<br />
* JDBC performance from the inside (Dave Cramer)<br />
* Growing with your Data (Richard Silva)</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Postgres_Open_2016&diff=28196Postgres Open 20162016-09-15T22:08:11Z<p>Dsteele: /* Wednesday September 14 */</p>
<hr />
<div>Conference website: [http://2016.postgresopen.org/ PostgresOpen 2016]<br />
<br />
[https://postgresopen.org/events/feedback/pgopen2016/ Conference Feedback]<br />
<br />
Events shown for placeholding purposes. See the "Editing help" for instructions on how to add a link to your slides.<br />
<br />
== Tuesday September 13 (Tutorials) ==<br />
* Introduction to PostGIS (Regina Obe and Leo Hsu)<br />
* Seamless failover with pgBouncer and Consul (Scott Mead)<br />
* Linux tuning to improve PostgreSQL performance: from hardware to postgresql.conf (Ilya Kosmodemiansky)<br />
* Advanced SQL + Functions (Joe Conway, Stephen Frost)<br />
* Autoscaling PostgreSQL with Kubernetes and OpenShift Part 1 (Jeff McCormick, Steven Pousty)<br />
<br />
== Wednesday September 14 ==<br />
* Digital Service Expert at the United States Digital Service, @USDS keynote (Marianne Bellotti)<br />
<br />
* A Look at the Elephant's Tail (Greg Stark)<br />
* A look at the Elephants trunk - PostgreSQL 9.6 (Magnus Hagander)<br />
* Flexible Indexing with Postgres (Bruce Momjian)<br />
* CREATE INDEX ... USING RUM. RUM index and its applications to FTS. (Oleg Bartunov)<br />
* Locked Up: Advances in Postgres Data Encryption (Vibhor Kumar)<br />
* Efficiently Backing up Terabytes of Data with pgBackRest (David Steele) [http://www.pgbackrest.org/media/slide/pgBackRest-PostgresOpen-2016.pdf]<br />
* [http://www.slideshare.net/SeanChittenden/dynamic-database-credentials-security-contingency-planning Assume database credentials have leaked: Dynamic Database credentials...] (Sean Chittenden) ([https://github.com/sean-/pgopen16-dyn-creds GitHub demo material])<br />
* You'd better have tested backups... (Dimitri Fontaine)<br />
* The Elephant Meets the Whale - Bringing PostgreSQL to Production on Docker (Phil Vacca)<br />
* Reviewing PostgreSQL Patches for Fun and Profit (David Steele)<br />
* Does Anybody Really Know What Time It Is? (Michael Alan Brewer)<br />
* PGLogical - the logical replication for PostgreSQL (Petr Jelinek)<br />
* Shall We Play a Game? (with CTEs) (James Coleman)<br />
* Performance Improvements in PostgreSQL 9.5, 9.6 and beyond (Tomas Vondra)<br />
* All the Big Data Sciency stuff you never knew Postgres could do (Jim Nasby)<br />
* Using PostGIS to Handle Geospatial Data as Vectors and Rasters (Dylan Herron)<br />
<br />
== Lightning Talks ==<br />
* [https://www.slideshare.net/SeanChittenden/postgres-on-zfs-lightning-talk PostgreSQL on ZFS], Sean Chittenden<br />
<br />
== Thursday, September 15 ==<br />
<br />
* [http://www.pateldenish.com/2016/09/advanced-postgres-monitoring.html Advanced Postgres Monitoring] (Denish Patel)<br />
* An opinionated guide to PostgreSQL replication (Peter Eisentraut)<br />
* Amazon RDS for PostgreSQL: New Features and Lessons Learned (Grant McAlister)<br />
* PostgreSQL Backups the modern ways (Magnus Hagander)<br />
* Big Data with PostgreSQL (Simon Riggs)<br />
* PostgreSQL worst practices (Ilya Kosmodemiansky)<br />
* Using PostgreSQL in a Small Business (Preston Hagar)<br />
* Administering Postgres using Docker and Openshift (Jeff McCormick)<br />
* Permissions in Postgres (Nathan Wagner)<br />
* Elephant Herd as a Service: Managing Hundreds of Postgres Instances (Shaun Thomas)<br />
* Managing OS Provided PostgreSQL Packages (Keith Fiske)<br />
* Data Architecture with PostgreSQL (Kevin Kempter)<br />
* Bitemporal Data Model: making it happened in Postgres (Henrietta Dombrovskaya)<br />
* [http://anarazel.de/talks/pgopen-dallas-2016-09-15/durability.pdf Understanding Durability in Postgres] (Andres Freund)<br />
* PostgreSQL with Chef & Puppet (Scott Mead)<br />
* Data Analysis with PL/Python (Keith Robertson)<br />
* JDBC performance from the inside (Dave Cramer)<br />
* Growing with your Data (Richard Silva)</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Postgres_Open_2016&diff=28195Postgres Open 20162016-09-15T22:07:54Z<p>Dsteele: /* Wednesday September 14 */</p>
<hr />
<div>Conference website: [http://2016.postgresopen.org/ PostgresOpen 2016]<br />
<br />
[https://postgresopen.org/events/feedback/pgopen2016/ Conference Feedback]<br />
<br />
Events shown for placeholding purposes. See the "Editing help" for instructions on how to add a link to your slides.<br />
<br />
== Tuesday September 13 (Tutorials) ==<br />
* Introduction to PostGIS (Regina Obe and Leo Hsu)<br />
* Seamless failover with pgBouncer and Consul (Scott Mead)<br />
* Linux tuning to improve PostgreSQL performance: from hardware to postgresql.conf (Ilya Kosmodemiansky)<br />
* Advanced SQL + Functions (Joe Conway, Stephen Frost)<br />
* Autoscaling PostgreSQL with Kubernetes and OpenShift Part 1 (Jeff McCormick, Steven Pousty)<br />
<br />
== Wednesday September 14 ==<br />
* Digital Service Expert at the United States Digital Service, @USDS keynote (Marianne Bellotti)<br />
<br />
* A Look at the Elephant's Tail (Greg Stark)<br />
* A look at the Elephants trunk - PostgreSQL 9.6 (Magnus Hagander)<br />
* Flexible Indexing with Postgres (Bruce Momjian)<br />
* CREATE INDEX ... USING RUM. RUM index and its applications to FTS. (Oleg Bartunov)<br />
* Locked Up: Advances in Postgres Data Encryption (Vibhor Kumar)<br />
* E�ciently Backing up Terabytes of Data with pgBackRest (David Steele) [http://www.pgbackrest.org/media/slide/pgBackRest-PostgresOpen-2016.pdf]<br />
* [http://www.slideshare.net/SeanChittenden/dynamic-database-credentials-security-contingency-planning Assume database credentials have leaked: Dynamic Database credentials...] (Sean Chittenden) ([https://github.com/sean-/pgopen16-dyn-creds GitHub demo material])<br />
* You'd better have tested backups... (Dimitri Fontaine)<br />
* The Elephant Meets the Whale - Bringing PostgreSQL to Production on Docker (Phil Vacca)<br />
* Reviewing PostgreSQL Patches for Fun and Profit (David Steele)<br />
* Does Anybody Really Know What Time It Is? (Michael Alan Brewer)<br />
* PGLogical - the logical replication for PostgreSQL (Petr Jelinek)<br />
* Shall We Play a Game? (with CTEs) (James Coleman)<br />
* Performance Improvements in PostgreSQL 9.5, 9.6 and beyond (Tomas Vondra)<br />
* All the Big Data Sciency stuff you never knew Postgres could do (Jim Nasby)<br />
* Using PostGIS to Handle Geospatial Data as Vectors and Rasters (Dylan Herron)<br />
<br />
== Lightning Talks ==<br />
* [https://www.slideshare.net/SeanChittenden/postgres-on-zfs-lightning-talk PostgreSQL on ZFS], Sean Chittenden<br />
<br />
== Thursday, September 15 ==<br />
<br />
* [http://www.pateldenish.com/2016/09/advanced-postgres-monitoring.html Advanced Postgres Monitoring] (Denish Patel)<br />
* An opinionated guide to PostgreSQL replication (Peter Eisentraut)<br />
* Amazon RDS for PostgreSQL: New Features and Lessons Learned (Grant McAlister)<br />
* PostgreSQL Backups the modern ways (Magnus Hagander)<br />
* Big Data with PostgreSQL (Simon Riggs)<br />
* PostgreSQL worst practices (Ilya Kosmodemiansky)<br />
* Using PostgreSQL in a Small Business (Preston Hagar)<br />
* Administering Postgres using Docker and Openshift (Jeff McCormick)<br />
* Permissions in Postgres (Nathan Wagner)<br />
* Elephant Herd as a Service: Managing Hundreds of Postgres Instances (Shaun Thomas)<br />
* Managing OS Provided PostgreSQL Packages (Keith Fiske)<br />
* Data Architecture with PostgreSQL (Kevin Kempter)<br />
* Bitemporal Data Model: making it happened in Postgres (Henrietta Dombrovskaya)<br />
* [http://anarazel.de/talks/pgopen-dallas-2016-09-15/durability.pdf Understanding Durability in Postgres] (Andres Freund)<br />
* PostgreSQL with Chef & Puppet (Scott Mead)<br />
* Data Analysis with PL/Python (Keith Robertson)<br />
* JDBC performance from the inside (Dave Cramer)<br />
* Growing with your Data (Richard Silva)</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PgConfUS_Talks_2016&diff=27452PgConfUS Talks 20162016-04-23T12:38:42Z<p>Dsteele: /* Grand Ballroom Salon B */</p>
<hr />
<div>= PGConf US 2016 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://www.pgconf.us/2016/<br />
<br />
== Videos ==<br />
<br />
https://www.youtube.com/pgconfus/<br />
<br />
== Trainings: Monday, 18 Apr 2016 ==<br />
<br />
* PostgreSQL When It is Not Your Job, Christophe Pettus<br />
* Linux tuning to improve PostgreSQL performance: from hardware to postgresql.conf, Ilya Kosmodemiansky<br />
* Steel Elephant: A Highly Secure PostgreSQL Environment with HashiCorp's Vault and Consul, Sean Chittenden<br />
* Introduction to PostGIS, Leo Hsu and Regina Obe<br />
* Out of the Box Replication in PostgreSQL 9.4, Denish Patel<br />
* Elevating Your Confidence with PostgreSQL's Restoration Capabilities!, Joshua D. Drake<br />
<br />
== Regulated Industry Summit: Monday, 18 Apr 2016 ==<br />
<br />
* State of Encryption, Privacy and Architecting for Scale, Will Ackerly, Founder, CTO, Virtru<br />
* Panel: Security, Compliance and IoT<br />
* Ideology and Licensing of Free and Open Source Software, Karen Sandler, Executive Director, Software Freedom Conservancy<br />
* Regulated Industries - Overview of New Drug Development and its Data Challenges, Dr. David P. Katz, Director - Life Sciences, KPMG<br />
* Healthcare & Regulations, Michael Ebert, Partner - Cyber Practice, KPMG<br />
* Roundtable: Can PostgreSQL become the world’s most advanced "enterprise" database?, PostgreSQL Core Team / Major Contributors<br />
* Panel: Modern Data Management for Enterprises, Bridging the SQL/NoSQL divide, Perspectives from MongoDB, PostgreSQL, Compose.io<br />
<br />
== Sessions: Tuesday, 19 Apr 2016 ==<br />
<br />
=== Grand Ballroom Salon A ===<br />
<br />
* Lessons Learned Operating Postgres at Scale, Dave Pirotte<br />
* An Availability Journey with MasterCard and PostgreSQL, John Young<br />
* [https://speakerdeck.com/lfittl/postgresql-at-a-web-startup Practical Lessons Learned when using PostgreSQL at a Web Startup], Lukas Fittl<br />
* ESA Sky: New window to the stars using PostgreSQL, Pilar de Teodoro<br />
* PostgreSQL in the Polyglot Enterprise, Mitch Pirtle<br />
<br />
=== Grand Ballroom Salon B ===<br />
<br />
* PostgreSQL Monitoring, Kevin Kempter<br />
* HawkEye On Postgresql, Adarsh Sharma<br />
* PostgreSQL High-Availability and Geographic Locality using consul, Sean Chittenden<br />
* Amazon RDS for PostgreSQL - Deep Dive on New Features and Learnings, Grant McAlister<br />
* HA PostgreSQL cluster with repmgr and pgbouncer, Jaime Casanova<br />
<br />
=== Grand Ballroom Salon C ===<br />
<br />
* PostgreSQL & Java: past, present and future, Alvaro Hernandez<br />
* Top 10 Problems Solved by PostGIS, Leo Hsu and Regina Obe<br />
* Overcoming First Principles: A guide for accessing the features of PostgreSQL in test-driven development, Eric Radman<br />
* PubSub with Postgresql, Gian Biondi<br />
* Predictive Analytics IN Postgres, Jim Nasby<br />
<br />
=== Northside Ballroom ===<br />
<br />
* PostgreSQL Development, Simon Riggs<br />
* How PostgreSQL is tested, Peter Eisentraut<br />
* Citus Architecture: Extending Postgres to Build a Distributed Database, Ozgun Erdogan<br />
* Deep dive into PostgreSQL statistics, Alexey Lesovsky<br />
* Sorting Through the Ages, Gregory Stark<br />
<br />
== Keynotes ==<br />
<br />
* Opening Keynote - Parag Goradia, Executive Director, Cloud Services Engineering, General Electric Digital<br />
* EnterpriseDB and Open Source, Robert Haas, Chief Database Architect, EnterpriseDB<br />
* BigSQL.org - The Best Way to Get Your PostgreSQL On, David Rader, Partner & VP Product Engineering, OpenSCG<br />
* Citus and the Cloud, Umur Cubukcu, CEO & Founder and Will Leinweber, Engineer at Citus Data<br />
* Hidden in the Docs: Connection Tunable Write Consistency, Chris Winslett, Platform Engineer, Compose<br />
<br />
== Sessions: Wednesday, 20 Apr 2016 ==<br />
<br />
=== Grand Ballroom Salon A ===<br />
<br />
* Using PostgreSQL to manage ArcGIS spatial data - Taking PostgreSQL and Analytics to the Next Level with Pythonm, Chaula Jain, Andy Eschbacher<br />
* Data Integration in the World of Microservices, Valentine Gogichashvili<br />
* On Providing Scalable Managed PostgreSQL services to Cloud Foundry, Xiujiao Gao<br />
* How Tencent uses Postgres-XC for their high volume WeChat payment system, Jasonys Li<br />
* [[Media:PGConfUS2016_Migrating_a_live_Postgres_database_into_RDS_with_no_downtime.pdf|Migrating a live Postgres database into RDS with no downtime: Experiences and Lessons Learned]], David Benoit<br />
* PostgreSQL HA Database Clusters through Containment, Quan-Ha Le<br />
<br />
=== Grand Ballroom Salon B ===<br />
<br />
* PostgreSQL DevOps with Chef & Puppet, Scott Mead<br />
* Achieving a State of Flow: Continuous Integration and Practical Event Sourcing w/ PostgreSQL, Paolo Lim<br />
* Kicking the Donkey of PostgreSQL Replication, Joshua D. Drake<br />
* [http://www.pgbackrest.org/media/slide/pgBackRest-PGConfUS-2016.pdf Efficiently Backing up Terabytes of Data with pgBackRest], David Steele<br />
* You'd better have tested backups, Dimitri Fontaine<br />
* PostgreSQL Power on Power, Michael Meskes<br />
<br />
=== Grand Ballroom Salon C ===<br />
<br />
* [http://www.joeconway.com/presentations/mls-postgres-pgconf.us-2016.pdf MLS PostgreSQL: Implementing Multi-level Security in PostgreSQL with RLS and SELinux], Joe Conway<br />
* Ranges, Partitioning and Limitations, Corey Huinker<br />
* That SQL looks pretty complicated. Where are the tests?, James E. Marca<br />
* PostgreSQL’s secret NoSQL superpowers, Amanda Gilmore<br />
* Programming the SQL Way with Common Table Expressions, Bruce Momjian<br />
* Deploying and Managing PostgreSQL with Ansible, David Hollenberger<br />
<br />
=== Northside Ballroom ===<br />
<br />
* SQL and MongoDB: how PostgreSQL brought them together, Asya Kamsky<br />
* How we made Greenplum Open Source, Andreas Scherbaum<br />
* Parallel Query In PostgreSQL, Robert Haas<br />
* [http://anarazel.de/talks/pgconf-nyc-2016-04-20/io.pdf IO in Postgres - Architecture, Tuning, Problems], Andres Freund<br />
* PostgreSQL Performance Presentation, 9.6devel Edition, Mark Wong<br />
* A look at the Elephants trunk - PostgreSQL 9.6, Magnus Hagander<br />
<br />
== Lightning Talks ==</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2015&diff=26322PostgreSQL Conference Europe Talks 20152015-11-04T12:52:50Z<p>Dsteele: /* Thursday */</p>
<hr />
<div><br />
== Tuesday (Trainings) ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Trainer||Title (Link to slides)<br />
|+<br />
| 09:00 - 17:00 || Ballroom A || Petr Jelinek, Simon Riggs || PostgreSQL Replication & Upgrades<br />
|+<br />
| 09:00 - 12:30 || Ballroom B || Hans-Jürgen Schönig || PostgreSQL performance tuning<br />
|+<br />
| 13:30 - 17:00 || Ballroom B || Joshua D. Drake || Elevating your confidence with the Elephant's restoration capabilities<br />
|+<br />
| 09:00 - 17:00 || Ballroom C || Stephen Frost || PostgreSQL Server Development<br />
|}<br />
<br />
<br />
== Wednesday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 09:45 - 10:45 || Ballroom A+B+C+D || Tamara Atanasoska || The bigger picture: More then just code<br />
|+<br />
| 11:10 - 12:00 || Ballroom A+B || Bruce Momjian || [http://momjian.us/main/writings/pgsql/features.pdf Upcoming PostgreSQL 9.5 Features]<br />
|+<br />
| 11:10 - 12:00 || Ballroom C+D || Mark Jones || Backup and Recovery using PITR<br />
|+<br />
| 11:10 - 12:00 || Palais I-III || Hans-Jürgen Schönig || Experimenting with semantic analysis<br />
|+<br />
| 12:10 - 13:00 || Ballroom A+B || Joe Conway || [http://www.joeconway.com/presentations/text_search-pgconfeu2015.pdf Where’s Waldo? - Text Search and Pattern Matching in PostgreSQL]<br />
|+<br />
| 12:10 - 13:00 || Ballroom C+D || Mladen Marinović || [https://bitbucket.org/marin/pgconfeu2015/raw/883632334c68663e10ab9637003f32bc2fadb279/Dockerizing%20a%20Largrer%20PostgreSQL%20Installation.pdf Dockerizing a Larger PostgreSQL Installation: What could possibly go wrong?]<br />
|+<br />
| 12:10 - 13:00 || Palais I-III || Nikolay Shaplov || [https://github.com/dhyannataraj/tuple-internals-presentation Tuple internals: exposing, exploring and explaining]<br />
|+<br />
| 14:00 - 14:50 || Ballroom A+B || Victor Blomqvist || [https://onedrive.live.com/redir?resid=AD5D909BDDBF9E98!34117&authkey=!AJQGy3wzRaFd_wo&ithint=file%2cpdf Location based dating in China - 0 to 100000000 daily swipes in a year]<br />
|+<br />
| 14:00 - 14:50 || Ballroom C+D || Kaarel Moppel || [https://docs.google.com/presentation/d/1BzzhJKHsie3cqjJwYa0y2QeTzMDsJtanbtsqq4As5tk/edit?usp=sharing A PostgreSQL DBA's toolbelt]<br />
|+<br />
| 14:00 - 14:50 || Palais I-III || Alexander Korotkov, Fedor Sigaev, Oleg Bartunov || Access method extendability in PostgreSQL or back to origin<br />
|+<br />
| 15:00 - 15:50 || Ballroom A+B || Michael Banck || [[Media: Dumping_the_mainframe_mbanck.pdf|Dumping the Mainframe: Migration Study from DB2 UDB to PostgreSQL]]<br />
|+<br />
| 15:00 - 15:50 || Ballroom C+D || Gulcin Yildirim || Managing PostgreSQL with Ansible<br />
|+<br />
| 15:00 - 15:50 || Palais I-III || Rubens Souza || [https://prezi.com/hf-3etd6ny0v/postgresql-on-the-raspberry-pi-2/ PostgreSQL on the Raspberry Pi 2]<br />
|+<br />
| 16:20 - 17:10 || Ballroom A+B || Simon Riggs || Serializable Transactions, Eventual Consistency and Really Scary Stuff<br />
|+<br />
| 16:20 - 17:10 || Ballroom C+D || Martín Marqués || HA strategy, properly done<br />
|+<br />
| 16:20 - 17:10 || Palais I-III || Jan Holčapek || cstore_fdw - turn you PostgreSQL into columnar store<br />
|+<br />
| 17:20 - 18:10 || Ballroom A+B || Boro Jakimovski & Dragan Sahpaski || [https://github.com/sorsix/pgconfeu2015 One National Health System - One Postgres Database (Architecture and Performance Review)]<br />
|+<br />
| 17:20 - 18:10 || Ballroom C+D || Tomas Vondra || Performance improvements in 9.5 and beyond<br />
|+<br />
| 17:20 - 18:10 || Palais I-III || Will Leinweber || Writing a Postgres Driver<br />
|}<br />
<br />
== Thursday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 09:30 - 10:20 || Ballroom A+B || Michael Paquier || [http://michael.otacoo.com/content/materials/20150917_pgopen2015_standbys.pdf WAL, Standbys and Postgrs 9.5]<br />
|+<br />
| 09:30 - 10:20 || Ballroom C+D || Grant McAlister || Amazon RDS for PostgreSQL - What's new and lessons learned<br />
|+<br />
| 09:30 - 10:20 || Palais I-III || Tomasz Rybak || Oracle to PostgreSQL: replication and migration<br />
|+<br />
| 10:30 - 11:20 || Ballroom A+B || Honza Horak || [https://github.com/hhorak/presentations/blob/master/2015/2015-database-containers-in-enterprise-world.pdf Database containers in enterprise world]<br />
|+<br />
| 10:30 - 11:20 || Ballroom C+D || Bruce Momjian || [http://momjian.us/main/writings/pgsql/locking.pdf Unlocking the Postgres Lock Manager]<br />
|+<br />
| 10:30 - 11:20 || Palais I-III || Robert Haas || Planning Parallel and Distributed Queries<br />
|+<br />
| 11:50 - 12:40 || Ballroom A+B || Balázs Bárány || [https://datascientist.at/wp-content/uploads/2015/01/B%C3%A1r%C3%A1ny-Data-Science-with-PostgreSQL.pdf Data Science with PostgreSQL]<br />
|+<br />
| 11:50 - 12:40 || Ballroom C+D || Simon Riggs || VACUUM, Freezing & Avoiding Wraparound<br />
|+<br />
| 11:50 - 12:40 || Palais I-III || Gianni Ciolli || The Importance of Query Profiling<br />
|+<br />
| 12:50 - 13:40 || Ballroom A+B || Stella Nisenbaum || Becoming a SQL Guru<br />
|+<br />
| 12:50 - 13:40 || Ballroom C+D || Gabriele Bartolini, Marco Nenciarini || [http://goo.gl/k9gyYf Integrating PostgreSQL with Logstash for real-time monitoring]<br />
|+<br />
| 12:50 - 13:40 || Palais I-III || Jim Mlodgenski || [http://www.slideshare.net/jim_mlodgenski/an-introduction-to-postresql-triggers An Introduction To PostgreSQL Triggers]<br />
|+<br />
| 14:40 - 15:30 || Ballroom A+B || Ilya Kosmodemiansky || Linux tuning to improve PostgreSQL performance<br />
|+<br />
| 14:40 - 15:30 || Ballroom C+D || David Steele || [https://github.com/dwsteele/conference/blob/release/HeavyDutyPgBackRest-PGConfEU-2015/slides.pdf Efficiently Backing up Terabytes of Data with PgBackRest]<br />
|+<br />
| 14:40 - 15:30 || Palais I-III || Andres Freund || [http://anarazel.de/talks/pgconf-eu-2015-10-29/profilingperf.pdf Profiling Postgres with Perf]<br />
|+<br />
| 15:40 - 16:30 || Ballroom A+B || Marco Slot || [https://drive.google.com/file/d/0B_mCJTCKj3AuX25UYVZ0aWpNWDQ/view?usp=sharing PostgreSQL as a Scalable Document Store]<br />
|+<br />
| 15:40 - 16:30 || Ballroom C+D || Tomas Vondra || PostgreSQL Performance on EXT4, XFS, F2FS, BTRFS and ZFS<br />
|+<br />
| 15:40 - 16:30 || Palais I-III || Anastasia Lubennikova || Indexes don't mean slow inserts.<br />
|+<br />
| 17:00 - 17:50 || Ballroom A+B+C+D || Harald Armin Massa || Lightning Talks<br />
|}<br />
<br />
== Friday ==<br />
<br />
{| class="wikitable"<br />
|Time||Room||Speaker||Title (Link to slides)<br />
|+<br />
| 09:30 - 10:20 || Ballroom A+B || Thomas Klausner || [http://domm.plix.at/talks/9_postgres_features_i_wish_i_learned_earlier.html 9 PostgreSQL features I wish I learned earlier ]<br />
|+<br />
| 09:30 - 10:20 || Ballroom C+D || Jim Mlodgenski || [http://www.slideshare.net/jim_mlodgenski/debugging-your-plpgsql-code Debugging Your PL/pgSQL Code ]<br />
|+<br />
| 09:30 - 10:20 || Palais I-III || KaiGai Kohei || [http://www.slideshare.net/kaigai/gpgpu-accelerates-postgresql-unlock-the-power-of-multithousand-cores GPGPU Accelerates PostgreSQL - Unlock the power of multi-thousand cores]<br />
|+<br />
| 10:50 - 11:40 || Ballroom A+B || Jonathan S. Katz || [http://www.slideshare.net/jkatz05/developing-and-deploying-apps-with-the-postgres-fdw Debugging My Love of Developing with the Postgres FDW...and how production tested those feelings ]<br />
|+<br />
| 10:50 - 11:40 || Ballroom C+D || Ilya Kosmodemiansky || Autovacuum, explained for engineers<br />
|+<br />
| 10:50 - 11:40 || Palais I-III || Ruben Gaspar Aparicio || [https://edms.cern.ch/file/1071302/1/PGSQL_DBoD_rubengaspar.pdf How to provide your own DBaaS: a practical story]<br />
|+<br />
| 11:50 - 12:40 || Ballroom A+B || Roland Sonnenschein || [http://de.slideshare.net/RolandSonnenschein/db-explorer Generic Editor for Hierarchical SQL Data Running in the Browser ]<br />
|+<br />
| 11:50 - 12:40 || Ballroom C+D || Andres Freund || [http://www.anarazel.de/talks/pgconf-eu-2015-10-30/concurrency.pdf Vertical Scalability in Postgres ]<br />
|+<br />
| 11:50 - 12:40 || Palais I-III || Vibhor Kumar || Locked Up: Advances in Postgres Data Encryption<br />
|+<br />
| 13:40 - 14:30 || Ballroom A+B || Vincent Picavet || [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2015/beyond_postgis_basics.pdf Beyond PostGIS basics : more spatial ! ]<br />
|+<br />
| 13:40 - 14:30 || Ballroom C+D || Gianni Ciolli || Automate High Availability using repmgr 3<br />
|+<br />
| 13:40 - 14:30 || Palais I-III || Heikki Linnakangas || [http://hlinnaka.iki.fi/presentations/Index-internals-Vienna2015.pdf Index Internals ]<br />
|+<br />
| 15:00 - 15:20 || Ballroom A+B+C+D || Robert Haas || The Elephants In The Room: Limitations of the PostgreSQL Core Technology<br />
|+<br />
| 15:25 - 15:45 || Ballroom A+B+C+D || Simon Riggs || PostgreSQL Core Roadmap<br />
|+<br />
| 15:50 - 16:10 || Ballroom A+B+C+D || Hans-Jürgen Schönig || 15 years of PostgreSQL consulting: Memories<br />
|+<br />
| 16:10 - 16:30 || Ballroom A+B+C+D || Dave Page, Magnus Hagander || [[media: PGConf.EU_2015_Closing.pdf|Closing Session ]]<br />
|}</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Postgres_Open_2015&diff=25872Postgres Open 20152015-09-18T21:15:17Z<p>Dsteele: /* Thursday September 17 */</p>
<hr />
<div>Conference website: [http://2015.postgresopen.org/ PostgresOpen 2015]<br />
<br />
[https://postgresopen.org/events/feedback/pgopen2015/ Conference Feedback]<br />
<br />
Events shown for placeholding purposes. See the "Editing help" for instructions on how to add a link to your slides.<br />
<br />
== Wednesday September 16 (Tutorials) ==<br />
* Hands-on Administration of PostgreSQL (Stephen Frost)<br />
* Big Postgres: Scaling PostgreSQL in a BigData environment (Jim Mlodgenski)<br />
* [https://github.com/jberkus/pgReplicationTutorial Binary Replication 101] (Josh Berkus)<br />
* Amazon RDS for PostgreSQL (Grant McAlister)<br />
<br />
== Thursday September 17 ==<br />
* [https://speakerdeck.com/williln/open-source-and-higher-education Open Source and Higher Education] Keynote (Lacey Williams Henschel)<br />
<br />
* [http://anarazel.de/talks/pgopen-dallas-2015-09-18/concurrency.pdf Improving postgres' concurrency] (Andres Freund)<br />
* Monitoring PostgreSQL (Kevin Kempter)<br />
* Welcome to Postgres! (Michael Alan Brewer)<br />
<br />
* [https://www.dropbox.com/sh/rb6ztde22ol4zhm/AAD9rpFHny70hfWS9s79Fyv0a?dl=0 All the Dirt on VACUUM] (Jim Nasby)<br />
* [http://www.joeconway.com/presentations/plr-pgopen2015.pdf Easy Statistical Analysis in PostgreSQL with PL/R] (Joe Conway)<br />
* What's new in PostgreSQL 9.5 (Magnus Hagander)<br />
<br />
* PostgreSQL Federation: Joining to Oracle, Mongo and more... (Jim Mlodgenski)<br />
* [http://www.joeconway.com/presentations/rds-pgopen2015.pdf Securing Your Database in Amazon RDS] (Sarah Conway)<br />
* [http://michael.otacoo.com/content/materials/20150917_pgopen2015_standbys.pdf WAL, standbys and Postgres 9.5] (Michael Paquier)<br />
<br />
* [[File:BECOMING_A_SQL_GURU.pdf]] (Stella Nisenbaum)<br />
* PostgreSQL Administration (Simon Riggs)<br />
* Using Postgres XL (Richard Silva)<br />
<br />
* [https://github.com/dwsteele/conference/blob/b3660bc8f338844a7c9d27549dfabeda5d94e321/slides.pdf Audit Logging for PostgreSQL] (David Steele)<br />
* [http://jberkus.github.io/explain_explained/index.html Explain Explained] (Josh Berkus)<br />
* Logical decoding: a new world of data exchange applications for PostgreSQL (Álvaro Hernández)<br />
<br />
== Lightning Talks ==<br />
* postgresql.us (Rob Treat)<br />
* Voting PostgreSQL (Magnus Hagander)<br />
* Better Constraints (James Coleman)<br />
* Sorting Improvements (Peter Geoghegan)<br />
* test_factory (Jim Nasby)<br />
* plpgsql dependencies (Steve Randall)<br />
<br />
== Friday, September 18 ==<br />
<br />
* [http://momjian.us/main/writings/pgsql/hw_selection.pdf Database Hardware Selection Guidelines] (Bruce Momjian)<br />
* [http://slides.keithf4.com/dontforget Don't Forget The Elephant] (Keith Fiske)<br />
* [https://wiki.postgresql.org/images/b/b6/PostgreSQL_in_Containers_at_Scale.pdf PostgreSQL in Containers at Scale] (Jeff McCormick, Steven Pousty)<br />
<br />
* 14 Calm Years of PostgreSQL in Critical Messaging (John Mason Scott)<br />
* PostgreSQL and Amazon RDS - What's new and lessons learned (Grant McAlister)<br />
* The Bones of Highly Available Postgres [[File:Bones_of_ha.pdf]] (Shaun Thomas)<br />
<br />
* PostgreSQL in PaxosLand: Distributed storage and strict consistency (Srivathsava Rangarajan)<br />
* PostgreSQL Scalability (Simon Riggs)<br />
* Streaming SQL with PipelineDB (Derek Nelson)<br />
<br />
* BDR From the Perspective of a QA Engineer (Simon Riggs)<br />
* PostgreSQL Performance & Benchmarking (Mark Wong)<br />
* UPSERT use cases (Peter Geoghegan)<br />
<br />
* A TARDIS for your ORM - application level time travel in PostgreSQL (Magnus Hagander)<br />
* Measurements, scales and encoding schemes (Joe Celko)<br />
* pg_classy: SQL Metacode System (code that writes code) (Jon Erdman (aka StuckMojo))<br />
<br />
* Creating PostgreSQL-as-a-Service at Scale (Sean Chittenden)<br />
* Pacemaker and PostgreSQL from the ground up (Brian Cosgrove)<br />
* Searching Text with PostgreSQL: A Primer (Phil Vacca)</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Postgres_Open_2015&diff=25870Postgres Open 20152015-09-18T21:11:12Z<p>Dsteele: /* Thursday September 17 */</p>
<hr />
<div>Conference website: [http://2015.postgresopen.org/ PostgresOpen 2015]<br />
<br />
[https://postgresopen.org/events/feedback/pgopen2015/ Conference Feedback]<br />
<br />
Events shown for placeholding purposes. See the "Editing help" for instructions on how to add a link to your slides.<br />
<br />
== Wednesday September 16 (Tutorials) ==<br />
* Hands-on Administration of PostgreSQL (Stephen Frost)<br />
* Big Postgres: Scaling PostgreSQL in a BigData environment (Jim Mlodgenski)<br />
* [https://github.com/jberkus/pgReplicationTutorial Binary Replication 101] (Josh Berkus)<br />
* Amazon RDS for PostgreSQL (Grant McAlister)<br />
<br />
== Thursday September 17 ==<br />
* [https://speakerdeck.com/williln/open-source-and-higher-education Open Source and Higher Education] Keynote (Lacey Williams Henschel)<br />
<br />
* [http://anarazel.de/talks/pgopen-dallas-2015-09-18/concurrency.pdf Improving postgres' concurrency] (Andres Freund)<br />
* Monitoring PostgreSQL (Kevin Kempter)<br />
* Welcome to Postgres! (Michael Alan Brewer)<br />
<br />
* All the Dirt on VACUUM (Jim Nasby)<br />
* [http://www.joeconway.com/presentations/plr-pgopen2015.pdf Easy Statistical Analysis in PostgreSQL with PL/R] (Joe Conway)<br />
* What's new in PostgreSQL 9.5 (Magnus Hagander)<br />
<br />
* PostgreSQL Federation: Joining to Oracle, Mongo and more... (Jim Mlodgenski)<br />
* [http://www.joeconway.com/presentations/rds-pgopen2015.pdf Securing Your Database in Amazon RDS] (Sarah Conway)<br />
* [http://michael.otacoo.com/content/materials/20150917_pgopen2015_standbys.pdf WAL, standbys and Postgres 9.5] (Michael Paquier)<br />
<br />
* [[File:BECOMING_A_SQL_GURU.pdf]] (Stella Nisenbaum)<br />
* PostgreSQL Administration (Simon Riggs)<br />
* Using Postgres XL (Richard Silva)<br />
<br />
* [https://github.com/dwsteele/conference/releases/tag/release/AuditLogging-PostgresOpen-2015 Audit Logging for PostgreSQL] (David Steele)<br />
* [http://jberkus.github.io/explain_explained/index.html Explain Explained] (Josh Berkus)<br />
* Logical decoding: a new world of data exchange applications for PostgreSQL (Álvaro Hernández)<br />
<br />
== Lightning Talks ==<br />
* postgresql.us (Rob Treat)<br />
* Voting PostgreSQL (Magnus Hagander)<br />
* Better Constraints (James Coleman)<br />
* Sorting Improvements (Peter Geoghegan)<br />
* test_factory (Jim Nasby)<br />
* plpgsql dependencies (Steve Randall)<br />
<br />
== Friday, September 18 ==<br />
<br />
* [http://momjian.us/main/writings/pgsql/hw_selection.pdf Database Hardware Selection Guidelines] (Bruce Momjian)<br />
* [http://slides.keithf4.com/dontforget Don't Forget The Elephant] (Keith Fiske)<br />
* [https://wiki.postgresql.org/images/b/b6/PostgreSQL_in_Containers_at_Scale.pdf PostgreSQL in Containers at Scale] (Jeff McCormick, Steven Pousty)<br />
<br />
* 14 Calm Years of PostgreSQL in Critical Messaging (John Mason Scott)<br />
* PostgreSQL and Amazon RDS - What's new and lessons learned (Grant McAlister)<br />
* The Bones of Highly Available Postgres [[File:Bones_of_ha.pdf]] (Shaun Thomas)<br />
<br />
* PostgreSQL in PaxosLand: Distributed storage and strict consistency (Srivathsava Rangarajan)<br />
* PostgreSQL Scalability (Simon Riggs)<br />
* Streaming SQL with PipelineDB (Derek Nelson)<br />
<br />
* BDR From the Perspective of a QA Engineer (Simon Riggs)<br />
* PostgreSQL Performance & Benchmarking (Mark Wong)<br />
* UPSERT use cases (Peter Geoghegan)<br />
<br />
* A TARDIS for your ORM - application level time travel in PostgreSQL (Magnus Hagander)<br />
* Measurements, scales and encoding schemes (Joe Celko)<br />
* pg_classy: SQL Metacode System (code that writes code) (Jon Erdman (aka StuckMojo))<br />
<br />
* Creating PostgreSQL-as-a-Service at Scale (Sean Chittenden)<br />
* Pacemaker and PostgreSQL from the ground up (Brian Cosgrove)<br />
* Searching Text with PostgreSQL: A Primer (Phil Vacca)</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Unconference&diff=24980PgCon 2015 Developer Unconference2015-06-12T17:49:00Z<p>Dsteele: /* Topics */</p>
<hr />
<div>An Unconference-style multi-track (three tracks are currently planned) event for active PostgreSQL developers will be held from the afternoon of Tuesday 16 June, 2015 through Wednesday 17 June 2015 at the University of Ottawa, as part of PGCon 2015. This Unconference will be focused on technical PostgreSQL development discussions ranging from Clustering and replication to the infrastructure which runs postgresql.org.<br />
<br />
'''Please add your name under RSVPs if you plan to attend.'''<br />
<br />
== Topics ==<br />
<br />
Developers are asked to propose topics which they wish to either present on or which they would like another individual to present on. All topics should be clearly related to PostgreSQL development. The topic should be added to the table below and any required attendees (presumably at least the presenter, and the requester if different) listed. Other attendees of the Unconference who are interested should list themselves as Optional. Note that non-technical topics related to PostgreSQL development will be addressed during the invite-only Developer meeting, being held in advance of the Unconference. Further, the Developer Unconference is for developers of PostgreSQL and user-oriented topics are not appropriate for this venue.<br />
<br />
== Slot assignment ==<br />
<br />
Slots will be assigned based on the topic's interest among the attendees of the Unconference (the number of individuals who listed themselves as attendees). Final determination on any particular topic will be made by the Unconference organizers. Please only participate if you are confident of your attendance at the Unconference.<br />
<br />
== Venue ==<br />
<br />
These meetings will be held at the University of Ottawa. The topics selected, the schedule and the specific room assignments will be published closer to the event and will be based on the information provided here. Please direct any questions to Dave Page (dpage@pgadmin.org).<br />
<br />
== Sponsorship ==<br />
<br />
The Developer Unconference will be sponsored by Salesforce.com, and by NTT Open Source for the Clustering Track.<br />
<br />
== Attendees ==<br />
<br />
While the Unconference is open to all attendees of PGCon, formal invitations will be sent to specific PostgreSQL developers, including the Core team, Major Contributors, Committers, and other developers who have been involved in the 9.4 release. These invitations are intended to encourage developers to attend the Unconference but we are unable to guarantee every invitee a speaking slot.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname):<br />
<br />
* Ashutosh Bapat<br />
* Oleg Bartunov<br />
* Josh Berkus<br />
* Jeff Davis<br />
* Ozgun Erdogan<br />
* Andres Freund<br />
* Stephen Frost<br />
* Masao Fujii<br />
* Etsuro Fujita<br />
* Peter Geoghegan<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Ahsan Hadi<br />
* Shigeru Hanada<br />
* Álvaro Herrera<br />
* Kyotaro Horiguchi<br />
* Thierry Husson (Wednesday @ 11am)<br />
* Ayumi Ishii<br />
* Stefan Kaltenbrunner<br />
* Amit Kapila<br />
* Konstantin Knizhnik<br />
* KaiGai Kohei (arrive tuesday evening)<br />
* Alexander Korotkov<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
* Grant McAlister<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Jim Nasby<br />
* Dave Page<br />
* Magnus Hagander<br />
* Kumar Rajeev Rastogi<br />
* Simon Riggs<br />
* Tetsuo Sakata<br />
* Masahiko Sawada<br />
* Marco Slot (Wednesday)<br />
* Greg Smith<br />
* Steve Singer (arrive tuesday mid-afternoon)<br />
* Tomas Vondra<br />
* Tatsuo Ishii<br />
* Yugo Nagata<br />
* Jan Wieck (arrive tuesday evening)<br />
* Joe Conway<br />
* Naoya Anzai (arrive tuesday evening)<br />
* David Steele (arrive tuesday evening)<br />
<br />
=Topics=<br />
<br />
'''Please add any topics you wish covered to the table.'''<br />
<br />
'''For any topics you are requesting or presenting on, please add your name in the Required column.'''<br />
<br />
'''For any topics you would like to attend, please add your name in the Interested column.'''<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Topic<br />
!Policy<br />
!Taker of Notes<br />
!Required Attendees<br />
!Interested Attendees<br />
<br />
|- style="background-color:lightgray;"<br />
|pgAdmin4<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost<br />
|Magnus Hagander, Joe Conway, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Infrastructure Q&A<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander, Joe Conway<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|WWW Team Meeting<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Advocacy Team Meeting<br />
|Open<br />
|<br />
|Stephen Frost<br />
|Magnus Hagander, Greg Smith, Jim Nasby, Josh Berkus, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Vertical Scalability w.r.t Writes<br />
|Open<br />
|Amit Kapila<br />
|Amit Kapila<br />
|Greg Smith, Hannu Valtonen, Ilya Kosmodemiansky, Tomas Vondra, Grant McAlister, Joe Conway, Kyotaro Horiguchi, Simon Riggs, Amit Langote, Andres Freund, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Security Team Meeting<br />
|Closed<br />
|<br />
|Heikki Linnakangas, Stephen Frost, Magnus Hagander<br />
|Noah Misch, Álvaro Herrera, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Compilation + LLVM<br />
|Open<br />
|<br />
|Kumar Rajeev Rastogi<br />
|Jeff Davis, Ozgun Erdogan, Tomas Vondra, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Horizontal Scalability / Sharding in PostgreSQL]] - ground covered so far and remaining to be covered. <br />
|Open<br />
|<br />
|Ahsan Hadi, Ashutosh Bapat, Etsuro Fujita<br />
|Hannu Valtonen, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Tetsuo Sakata, Simon Riggs, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PGCAC Board Meeting 2015]]<br />
|Open*<br />
|Josh Berkus<br />
|Josh Berkus, Chris Browne, Steve Singer, Dan Langille, Dave Page<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|pgPool2 towards version 3.5]]<br />
|Open<br />
|<br />
|Tatsuo Ishii<br />
|Ashutosh Bapat<br />
<br />
|- style="background-color:lightgray;"<br />
|Partitioning<br />
|Open<br />
|<br />
|Amit Langote<br />
|Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Kyotaro Horiguchi, KaiGai Kohei, Noah Misch, Tetsuo Sakata, Álvaro Herrera, Thierry Husson, Joe Conway, Naoya Anzai, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Foreign Data Wrapper enhancements]]<br />
|Open<br />
|<br />
|Shigeru Hanada, Etsuro Fujita<br />
|KaiGai Kohei, Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Noah Misch, Tetsuo Sakata, Naoya Anzai, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Utilization of modern semiconductor - GPU, SSD, NVRAM, FPGA, ...<br />
|Open<br />
|<br />
|KaiGai Kohei<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Columnar Storage<br />
|Open<br />
|<br />
|Álvaro Herrera<br />
|Ozgun Erdogan, Tomas Vondra, KaiGai Kohei, Amit Kapila, Josh Berkus, Naoya Anzai, Amit Langote, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Future of PostgreSQL shared-nothing cluster<br />
|Open<br />
|<br />
|Konstantin Knizhnik, Alexander Korotkov, Oleg Bartunov<br />
|Jeff Davis, Amit Langote, Kumar Rajeev Rastogi, Josh Berkus, Simon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PostgreSQL and SMR Drives]] - the future of magnetic storage means very expensive random writes<br />
|Open<br />
|<br />
|Jeff Davis<br />
|Kumar Rajeev Rastogi, Noah Misch, Ilya Kosmodemiansky, Amit Kapila, Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Slony Development]]<br />
|Open<br />
|<br />
| Steve Singer, Chris Browne, Jan Wieck<br />
| Josh Berkus<br />
<br />
|- style="background-color:lightgray;"<br />
|[[DockerizingPostgres|Dockerizing Postgres]]<br />
|Open<br />
|<br />
| Josh Berkus<br />
| Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Bi Directional Replication & Logical Decoding|BDR]]<br />
|Open<br />
|<br />
| Simon Riggs<br />
| Andres Freund<br />
<br />
|- style="background-color:lightgray;"<br />
|Autonomous Transactions<br />
|Open<br />
|<br />
| Simon Riggs, Kumar Rajeev Rastogi<br />
| David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Audit Logging<br />
|Open<br />
|<br />
| David Steele<br />
|<br />
<br />
|}<br />
<br />
== pgAdmin4 ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Infrastructure Q&A ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== WWW Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Advocacy Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Vertical Scalability w.r.t Writes ==<br />
Purpose of this discussion:<br />
* Discuss about priority/importance of various performance and scalability problems<br />
* Solution/Idea to solve most important problem('s)<br />
* Is pgbench sufficient to capture various kind of real world workloads?<br />
<br />
Some of important performance problems I have in mind are:<br />
* Avoid/Reduce Vacuum Freeze<br />
* Bloat<br />
Heap<br />
Index<br />
* Instability in TPS due to checkpointer flush<br />
* Tuple size<br />
Heap Tuple Header <br />
Alignment in index can lead to bigger index size for simple datatypes<br />
Scalability bottlenecks<br />
* Locks<br />
ProcArrayLock<br />
WALWriteLock<br />
CLOGControlLock<br />
Lock for Relation Extension<br />
<br />
* Writes, especially when data doesn't fit in shared buffers.<br />
Write Performance<br />
Double Buffering<br />
In-memory table/tablespaces<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Security Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* This will be, ehem, secure so nothing will be written here<br />
<br />
== Partitioning ==<br />
Proposal to enhance partitioning support in PostgreSQL was posted to -hackers last year and resulted in discussion of some ideas regarding implementation. Late in the discussion, a crude WIP patch was also posted with some experimental syntax, catalog changes, an idea for internal representation and a proof-of-concept INSERT tuple routing function demonstrating practicality of the internal representation. It would be nice to carry the discussion forward at the same time implementing a patch to be proposed, reviewed early in the 9.6 development cycle. Points to discuss could be: <br />
<br />
* New features and old inheritance based implementation<br />
* Planner considerations for new partitioned table<br />
* Need for a new Append-like executor node for partitioned tables<br />
* DML/DDL restrictions on partitioned tables and partitions<br />
* Basically any considerations for partitioned tables and partitions that are explicitly defined so at a layer that's above the storage layer<br />
* Other points that come up<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Utilization of modern semiconductor ==<br />
Recent evolution of semiconductor devices make us re-consider the assumption we stand on, and utilization of its power is key of innovation.<br />
We'd like to have a discussion to get the future direction in short and middle/long term.<br />
<br />
* GPU, FPGA - have advantage on simple but massive amount of calculation. It allows DBMS to perform as data processing platform that works nearby data.<br />
<br />
* SSD, NVRAM - likely, game changer of storage layer on both of read/write workloads. DBMS also has to pay attention characteristics of these devices.<br />
<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Future of PostgreSQL shared-nothing cluster ==<br />
<br />
=== Meeting Notes ===<br />
In 2015 PostgreSQL Professional company started project of migration PostgreSQL-XL to codebase of PostgreSQL 9.4 and increasing its stability and usability. At this unconference session we'd like to discuss current progress and further development. Generally we'd like to find ways to reduce difference between PostgreSQL and its shared-nothing cluster fork so that burden of the maintenance become manageable. <br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== PostgreSQL and SMR Drives ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Native Columnar Storage ==<br />
<br />
See Alvaro's [http://www.postgresql.org/message-id/20150611230316.GM133018@postgresql.org email to Hackers].<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Audit Logging ==<br />
<br />
Audit logging is an important part of a RDBMS for many users and applications. Discuss how best to incorporate audit logging into PostgreSQL and what must be included at a minimum to make the feature viable. <br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Unconference&diff=24978PgCon 2015 Developer Unconference2015-06-12T17:44:55Z<p>Dsteele: /* Topics */</p>
<hr />
<div>An Unconference-style multi-track (three tracks are currently planned) event for active PostgreSQL developers will be held from the afternoon of Tuesday 16 June, 2015 through Wednesday 17 June 2015 at the University of Ottawa, as part of PGCon 2015. This Unconference will be focused on technical PostgreSQL development discussions ranging from Clustering and replication to the infrastructure which runs postgresql.org.<br />
<br />
'''Please add your name under RSVPs if you plan to attend.'''<br />
<br />
== Topics ==<br />
<br />
Developers are asked to propose topics which they wish to either present on or which they would like another individual to present on. All topics should be clearly related to PostgreSQL development. The topic should be added to the table below and any required attendees (presumably at least the presenter, and the requester if different) listed. Other attendees of the Unconference who are interested should list themselves as Optional. Note that non-technical topics related to PostgreSQL development will be addressed during the invite-only Developer meeting, being held in advance of the Unconference. Further, the Developer Unconference is for developers of PostgreSQL and user-oriented topics are not appropriate for this venue.<br />
<br />
== Slot assignment ==<br />
<br />
Slots will be assigned based on the topic's interest among the attendees of the Unconference (the number of individuals who listed themselves as attendees). Final determination on any particular topic will be made by the Unconference organizers. Please only participate if you are confident of your attendance at the Unconference.<br />
<br />
== Venue ==<br />
<br />
These meetings will be held at the University of Ottawa. The topics selected, the schedule and the specific room assignments will be published closer to the event and will be based on the information provided here. Please direct any questions to Dave Page (dpage@pgadmin.org).<br />
<br />
== Sponsorship ==<br />
<br />
The Developer Unconference will be sponsored by Salesforce.com, and by NTT Open Source for the Clustering Track.<br />
<br />
== Attendees ==<br />
<br />
While the Unconference is open to all attendees of PGCon, formal invitations will be sent to specific PostgreSQL developers, including the Core team, Major Contributors, Committers, and other developers who have been involved in the 9.4 release. These invitations are intended to encourage developers to attend the Unconference but we are unable to guarantee every invitee a speaking slot.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname):<br />
<br />
* Ashutosh Bapat<br />
* Oleg Bartunov<br />
* Josh Berkus<br />
* Jeff Davis<br />
* Ozgun Erdogan<br />
* Andres Freund<br />
* Stephen Frost<br />
* Masao Fujii<br />
* Etsuro Fujita<br />
* Peter Geoghegan<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Ahsan Hadi<br />
* Shigeru Hanada<br />
* Álvaro Herrera<br />
* Kyotaro Horiguchi<br />
* Thierry Husson (Wednesday @ 11am)<br />
* Ayumi Ishii<br />
* Stefan Kaltenbrunner<br />
* Amit Kapila<br />
* Konstantin Knizhnik<br />
* KaiGai Kohei (arrive tuesday evening)<br />
* Alexander Korotkov<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
* Grant McAlister<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Jim Nasby<br />
* Dave Page<br />
* Magnus Hagander<br />
* Kumar Rajeev Rastogi<br />
* Simon Riggs<br />
* Tetsuo Sakata<br />
* Masahiko Sawada<br />
* Marco Slot (Wednesday)<br />
* Greg Smith<br />
* Steve Singer (arrive tuesday mid-afternoon)<br />
* Tomas Vondra<br />
* Tatsuo Ishii<br />
* Yugo Nagata<br />
* Jan Wieck (arrive tuesday evening)<br />
* Joe Conway<br />
* Naoya Anzai (arrive tuesday evening)<br />
* David Steele (arrive tuesday evening)<br />
<br />
=Topics=<br />
<br />
'''Please add any topics you wish covered to the table.'''<br />
<br />
'''For any topics you are requesting or presenting on, please add your name in the Required column.'''<br />
<br />
'''For any topics you would like to attend, please add your name in the Interested column.'''<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Topic<br />
!Policy<br />
!Taker of Notes<br />
!Required Attendees<br />
!Interested Attendees<br />
<br />
|- style="background-color:lightgray;"<br />
|pgAdmin4<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost<br />
|Magnus Hagander, Joe Conway, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Infrastructure Q&A<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander, Joe Conway<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|WWW Team Meeting<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Advocacy Team Meeting<br />
|Open<br />
|<br />
|Stephen Frost<br />
|Magnus Hagander, Greg Smith, Jim Nasby, Josh Berkus, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Vertical Scalability w.r.t Writes<br />
|Open<br />
|Amit Kapila<br />
|Amit Kapila<br />
|Greg Smith, Hannu Valtonen, Ilya Kosmodemiansky, Tomas Vondra, Grant McAlister, Joe Conway, Kyotaro Horiguchi, Simon Riggs, Amit Langote, Andres Freund, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Security Team Meeting<br />
|Closed<br />
|<br />
|Heikki Linnakangas, Stephen Frost, Magnus Hagander<br />
|Noah Misch, Álvaro Herrera, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Compilation + LLVM<br />
|Open<br />
|<br />
|Kumar Rajeev Rastogi<br />
|Jeff Davis, Ozgun Erdogan, Tomas Vondra, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Horizontal Scalability / Sharding in PostgreSQL]] - ground covered so far and remaining to be covered. <br />
|Open<br />
|<br />
|Ahsan Hadi, Ashutosh Bapat, Etsuro Fujita<br />
|Hannu Valtonen, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Tetsuo Sakata, SImon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PGCAC Board Meeting 2015]]<br />
|Open*<br />
|Josh Berkus<br />
|Josh Berkus, Chris Browne, Steve Singer, Dan Langille, Dave Page<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|pgPool2 towards version 3.5]]<br />
|Open<br />
|<br />
|Tatsuo Ishii<br />
|Ashutosh Bapat<br />
<br />
|- style="background-color:lightgray;"<br />
|Partitioning<br />
|Open<br />
|<br />
|Amit Langote<br />
|Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Kyotaro Horiguchi, KaiGai Kohei, Noah Misch, Tetsuo Sakata, Álvaro Herrera, Thierry Husson, Joe Conway, Naoya Anzai, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Foreign Data Wrapper enhancements]]<br />
|Open<br />
|<br />
|Shigeru Hanada, Etsuro Fujita<br />
|KaiGai Kohei, Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Noah Misch, Tetsuo Sakata, Naoya Anzai, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Utilization of modern semiconductor - GPU, SSD, NVRAM, FPGA, ...<br />
|Open<br />
|<br />
|KaiGai Kohei<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Columnar Storage<br />
|Open<br />
|<br />
|Álvaro Herrera<br />
|Ozgun Erdogan, Tomas Vondra, KaiGai Kohei, Amit Kapila, Josh Berkus, Naoya Anzai, Amit Langote, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Future of PostgreSQL shared-nothing cluster<br />
|Open<br />
|<br />
|Konstantin Knizhnik, Alexander Korotkov, Oleg Bartunov<br />
|Jeff Davis, Amit Langote, Kumar Rajeev Rastogi, Josh Berkus, Simon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PostgreSQL and SMR Drives]] - the future of magnetic storage means very expensive random writes<br />
|Open<br />
|<br />
|Jeff Davis<br />
|Kumar Rajeev Rastogi, Noah Misch, Ilya Kosmodemiansky, Amit Kapila, Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Slony Development]]<br />
|Open<br />
|<br />
| Steve Singer, Chris Browne, Jan Wieck<br />
| Josh Berkus<br />
<br />
|- style="background-color:lightgray;"<br />
|[[DockerizingPostgres|Dockerizing Postgres]]<br />
|Open<br />
|<br />
| Josh Berkus<br />
| Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[Bi Directional Replication & Logical Decoding|Bi Directional Replication & Logical Decoding|BDR]]<br />
|Open<br />
|<br />
| Simon Riggs<br />
| Andres Freund<br />
<br />
|- style="background-color:lightgray;"<br />
|Autonomous Transactions<br />
|Open<br />
|<br />
| Simon Riggs, Kumar Rajeev Rastogi<br />
| David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Audit Logging<br />
|Open<br />
|<br />
| David Steele<br />
|<br />
<br />
|}<br />
<br />
== pgAdmin4 ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Infrastructure Q&A ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== WWW Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Advocacy Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Vertical Scalability w.r.t Writes ==<br />
Purpose of this discussion:<br />
* Discuss about priority/importance of various performance and scalability problems<br />
* Solution/Idea to solve most important problem('s)<br />
* Is pgbench sufficient to capture various kind of real world workloads?<br />
<br />
Some of important performance problems I have in mind are:<br />
* Avoid/Reduce Vacuum Freeze<br />
* Bloat<br />
Heap<br />
Index<br />
* Instability in TPS due to checkpointer flush<br />
* Tuple size<br />
Heap Tuple Header <br />
Alignment in index can lead to bigger index size for simple datatypes<br />
Scalability bottlenecks<br />
* Locks<br />
ProcArrayLock<br />
WALWriteLock<br />
CLOGControlLock<br />
Lock for Relation Extension<br />
<br />
* Writes, especially when data doesn't fit in shared buffers.<br />
Write Performance<br />
Double Buffering<br />
In-memory table/tablespaces<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Security Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* This will be, ehem, secure so nothing will be written here<br />
<br />
== Partitioning ==<br />
Proposal to enhance partitioning support in PostgreSQL was posted to -hackers last year and resulted in discussion of some ideas regarding implementation. Late in the discussion, a crude WIP patch was also posted with some experimental syntax, catalog changes, an idea for internal representation and a proof-of-concept INSERT tuple routing function demonstrating practicality of the internal representation. It would be nice to carry the discussion forward at the same time implementing a patch to be proposed, reviewed early in the 9.6 development cycle. Points to discuss could be: <br />
<br />
* New features and old inheritance based implementation<br />
* Planner considerations for new partitioned table<br />
* Need for a new Append-like executor node for partitioned tables<br />
* DML/DDL restrictions on partitioned tables and partitions<br />
* Basically any considerations for partitioned tables and partitions that are explicitly defined so at a layer that's above the storage layer<br />
* Other points that come up<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Utilization of modern semiconductor ==<br />
Recent evolution of semiconductor devices make us re-consider the assumption we stand on, and utilization of its power is key of innovation.<br />
We'd like to have a discussion to get the future direction in short and middle/long term.<br />
<br />
* GPU, FPGA - have advantage on simple but massive amount of calculation. It allows DBMS to perform as data processing platform that works nearby data.<br />
<br />
* SSD, NVRAM - likely, game changer of storage layer on both of read/write workloads. DBMS also has to pay attention characteristics of these devices.<br />
<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Future of PostgreSQL shared-nothing cluster ==<br />
<br />
=== Meeting Notes ===<br />
In 2015 PostgreSQL Professional company started project of migration PostgreSQL-XL to codebase of PostgreSQL 9.4 and increasing its stability and usability. At this unconference session we'd like to discuss current progress and further development. Generally we'd like to find ways to reduce difference between PostgreSQL and its shared-nothing cluster fork so that burden of the maintenance become manageable. <br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== PostgreSQL and SMR Drives ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Native Columnar Storage ==<br />
<br />
See Alvaro's [http://www.postgresql.org/message-id/20150611230316.GM133018@postgresql.org email to Hackers].<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Audit Logging ==<br />
<br />
Audit logging is an important part of a RDBMS for many users and applications. Discuss how best to incorporate audit logging into PostgreSQL and what must be included at a minimum to make the feature viable. <br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Unconference&diff=24977PgCon 2015 Developer Unconference2015-06-12T17:42:26Z<p>Dsteele: /* Topics */</p>
<hr />
<div>An Unconference-style multi-track (three tracks are currently planned) event for active PostgreSQL developers will be held from the afternoon of Tuesday 16 June, 2015 through Wednesday 17 June 2015 at the University of Ottawa, as part of PGCon 2015. This Unconference will be focused on technical PostgreSQL development discussions ranging from Clustering and replication to the infrastructure which runs postgresql.org.<br />
<br />
'''Please add your name under RSVPs if you plan to attend.'''<br />
<br />
== Topics ==<br />
<br />
Developers are asked to propose topics which they wish to either present on or which they would like another individual to present on. All topics should be clearly related to PostgreSQL development. The topic should be added to the table below and any required attendees (presumably at least the presenter, and the requester if different) listed. Other attendees of the Unconference who are interested should list themselves as Optional. Note that non-technical topics related to PostgreSQL development will be addressed during the invite-only Developer meeting, being held in advance of the Unconference. Further, the Developer Unconference is for developers of PostgreSQL and user-oriented topics are not appropriate for this venue.<br />
<br />
== Slot assignment ==<br />
<br />
Slots will be assigned based on the topic's interest among the attendees of the Unconference (the number of individuals who listed themselves as attendees). Final determination on any particular topic will be made by the Unconference organizers. Please only participate if you are confident of your attendance at the Unconference.<br />
<br />
== Venue ==<br />
<br />
These meetings will be held at the University of Ottawa. The topics selected, the schedule and the specific room assignments will be published closer to the event and will be based on the information provided here. Please direct any questions to Dave Page (dpage@pgadmin.org).<br />
<br />
== Sponsorship ==<br />
<br />
The Developer Unconference will be sponsored by Salesforce.com, and by NTT Open Source for the Clustering Track.<br />
<br />
== Attendees ==<br />
<br />
While the Unconference is open to all attendees of PGCon, formal invitations will be sent to specific PostgreSQL developers, including the Core team, Major Contributors, Committers, and other developers who have been involved in the 9.4 release. These invitations are intended to encourage developers to attend the Unconference but we are unable to guarantee every invitee a speaking slot.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname):<br />
<br />
* Ashutosh Bapat<br />
* Oleg Bartunov<br />
* Josh Berkus<br />
* Jeff Davis<br />
* Ozgun Erdogan<br />
* Andres Freund<br />
* Stephen Frost<br />
* Masao Fujii<br />
* Etsuro Fujita<br />
* Peter Geoghegan<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Ahsan Hadi<br />
* Shigeru Hanada<br />
* Álvaro Herrera<br />
* Kyotaro Horiguchi<br />
* Thierry Husson (Wednesday @ 11am)<br />
* Ayumi Ishii<br />
* Stefan Kaltenbrunner<br />
* Amit Kapila<br />
* Konstantin Knizhnik<br />
* KaiGai Kohei (arrive tuesday evening)<br />
* Alexander Korotkov<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
* Grant McAlister<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Jim Nasby<br />
* Dave Page<br />
* Magnus Hagander<br />
* Kumar Rajeev Rastogi<br />
* Simon Riggs<br />
* Tetsuo Sakata<br />
* Masahiko Sawada<br />
* Marco Slot (Wednesday)<br />
* Greg Smith<br />
* Steve Singer (arrive tuesday mid-afternoon)<br />
* Tomas Vondra<br />
* Tatsuo Ishii<br />
* Yugo Nagata<br />
* Jan Wieck (arrive tuesday evening)<br />
* Joe Conway<br />
* Naoya Anzai (arrive tuesday evening)<br />
* David Steele (arrive tuesday evening)<br />
<br />
=Topics=<br />
<br />
'''Please add any topics you wish covered to the table.'''<br />
<br />
'''For any topics you are requesting or presenting on, please add your name in the Required column.'''<br />
<br />
'''For any topics you would like to attend, please add your name in the Interested column.'''<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Topic<br />
!Policy<br />
!Taker of Notes<br />
!Required Attendees<br />
!Interested Attendees<br />
<br />
|- style="background-color:lightgray;"<br />
|pgAdmin4<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost<br />
|Magnus Hagander, Joe Conway, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Infrastructure Q&A<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander, Joe Conway<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|WWW Team Meeting<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Advocacy Team Meeting<br />
|Open<br />
|<br />
|Stephen Frost<br />
|Magnus Hagander, Greg Smith, Jim Nasby, Josh Berkus, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Vertical Scalability w.r.t Writes<br />
|Open<br />
|Amit Kapila<br />
|Amit Kapila<br />
|Greg Smith, Hannu Valtonen, Ilya Kosmodemiansky, Tomas Vondra, Grant McAlister, Joe Conway, Kyotaro Horiguchi, Simon Riggs, Amit Langote, Andres Freund, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Security Team Meeting<br />
|Closed<br />
|<br />
|Heikki Linnakangas, Stephen Frost, Magnus Hagander<br />
|Noah Misch, Álvaro Herrera, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Compilation + LLVM<br />
|Open<br />
|<br />
|Kumar Rajeev Rastogi<br />
|Jeff Davis, Ozgun Erdogan, Tomas Vondra, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Horizontal Scalability / Sharding in PostgreSQL]] - ground covered so far and remaining to be covered. <br />
|Open<br />
|<br />
|Ahsan Hadi, Ashutosh Bapat, Etsuro Fujita<br />
|Hannu Valtonen, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Tetsuo Sakata, SImon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PGCAC Board Meeting 2015]]<br />
|Open*<br />
|Josh Berkus<br />
|Josh Berkus, Chris Browne, Steve Singer, Dan Langille, Dave Page<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|pgPool2 towards version 3.5]]<br />
|Open<br />
|<br />
|Tatsuo Ishii<br />
|Ashutosh Bapat<br />
<br />
|- style="background-color:lightgray;"<br />
|Partitioning<br />
|Open<br />
|<br />
|Amit Langote<br />
|Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Kyotaro Horiguchi, KaiGai Kohei, Noah Misch, Tetsuo Sakata, Álvaro Herrera, Thierry Husson, Joe Conway, Naoya Anzai, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Foreign Data Wrapper enhancements]]<br />
|Open<br />
|<br />
|Shigeru Hanada, Etsuro Fujita<br />
|KaiGai Kohei, Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Noah Misch, Tetsuo Sakata, Naoya Anzai, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Utilization of modern semiconductor - GPU, SSD, NVRAM, FPGA, ...<br />
|Open<br />
|<br />
|KaiGai Kohei<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Columnar Storage<br />
|Open<br />
|<br />
|Álvaro Herrera<br />
|Ozgun Erdogan, Tomas Vondra, KaiGai Kohei, Amit Kapila, Josh Berkus, Naoya Anzai, Amit Langote, Robert Haas, David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Future of PostgreSQL shared-nothing cluster<br />
|Open<br />
|<br />
|Konstantin Knizhnik, Alexander Korotkov, Oleg Bartunov<br />
|Jeff Davis, Amit Langote, Kumar Rajeev Rastogi, Josh Berkus, Simon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PostgreSQL and SMR Drives]] - the future of magnetic storage means very expensive random writes<br />
|Open<br />
|<br />
|Jeff Davis<br />
|Kumar Rajeev Rastogi, Noah Misch, Ilya Kosmodemiansky, Amit Kapila, Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Slony Development]]<br />
|Open<br />
|<br />
| Steve Singer, Chris Browne, Jan Wieck<br />
| Josh Berkus<br />
<br />
|- style="background-color:lightgray;"<br />
|[[DockerizingPostgres|Dockerizing Postgres]]<br />
|Open<br />
|<br />
| Josh Berkus<br />
| Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[Bi Directional Replication & Logical Decoding|Bi Directional Replication & Logical Decoding|BDR]]<br />
|Open<br />
|<br />
| Simon Riggs<br />
| Andres Freund<br />
<br />
|- style="background-color:lightgray;"<br />
|Autonomous Transactions<br />
|Open<br />
|<br />
| Simon Riggs, Kumar Rajeev Rastogi<br />
| David Steele<br />
<br />
|- style="background-color:lightgray;"<br />
|Audit Logging<br />
|Open<br />
|<br />
| David Steele<br />
|<br />
<br />
|}<br />
<br />
== pgAdmin4 ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Infrastructure Q&A ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== WWW Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Advocacy Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Vertical Scalability w.r.t Writes ==<br />
Purpose of this discussion:<br />
* Discuss about priority/importance of various performance and scalability problems<br />
* Solution/Idea to solve most important problem('s)<br />
* Is pgbench sufficient to capture various kind of real world workloads?<br />
<br />
Some of important performance problems I have in mind are:<br />
* Avoid/Reduce Vacuum Freeze<br />
* Bloat<br />
Heap<br />
Index<br />
* Instability in TPS due to checkpointer flush<br />
* Tuple size<br />
Heap Tuple Header <br />
Alignment in index can lead to bigger index size for simple datatypes<br />
Scalability bottlenecks<br />
* Locks<br />
ProcArrayLock<br />
WALWriteLock<br />
CLOGControlLock<br />
Lock for Relation Extension<br />
<br />
* Writes, especially when data doesn't fit in shared buffers.<br />
Write Performance<br />
Double Buffering<br />
In-memory table/tablespaces<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Security Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* This will be, ehem, secure so nothing will be written here<br />
<br />
== Partitioning ==<br />
Proposal to enhance partitioning support in PostgreSQL was posted to -hackers last year and resulted in discussion of some ideas regarding implementation. Late in the discussion, a crude WIP patch was also posted with some experimental syntax, catalog changes, an idea for internal representation and a proof-of-concept INSERT tuple routing function demonstrating practicality of the internal representation. It would be nice to carry the discussion forward at the same time implementing a patch to be proposed, reviewed early in the 9.6 development cycle. Points to discuss could be: <br />
<br />
* New features and old inheritance based implementation<br />
* Planner considerations for new partitioned table<br />
* Need for a new Append-like executor node for partitioned tables<br />
* DML/DDL restrictions on partitioned tables and partitions<br />
* Basically any considerations for partitioned tables and partitions that are explicitly defined so at a layer that's above the storage layer<br />
* Other points that come up<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Utilization of modern semiconductor ==<br />
Recent evolution of semiconductor devices make us re-consider the assumption we stand on, and utilization of its power is key of innovation.<br />
We'd like to have a discussion to get the future direction in short and middle/long term.<br />
<br />
* GPU, FPGA - have advantage on simple but massive amount of calculation. It allows DBMS to perform as data processing platform that works nearby data.<br />
<br />
* SSD, NVRAM - likely, game changer of storage layer on both of read/write workloads. DBMS also has to pay attention characteristics of these devices.<br />
<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Future of PostgreSQL shared-nothing cluster ==<br />
<br />
=== Meeting Notes ===<br />
In 2015 PostgreSQL Professional company started project of migration PostgreSQL-XL to codebase of PostgreSQL 9.4 and increasing its stability and usability. At this unconference session we'd like to discuss current progress and further development. Generally we'd like to find ways to reduce difference between PostgreSQL and its shared-nothing cluster fork so that burden of the maintenance become manageable. <br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== PostgreSQL and SMR Drives ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Native Columnar Storage ==<br />
<br />
See Alvaro's [http://www.postgresql.org/message-id/20150611230316.GM133018@postgresql.org email to Hackers].<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Unconference&diff=24976PgCon 2015 Developer Unconference2015-06-12T17:40:45Z<p>Dsteele: /* Topics */</p>
<hr />
<div>An Unconference-style multi-track (three tracks are currently planned) event for active PostgreSQL developers will be held from the afternoon of Tuesday 16 June, 2015 through Wednesday 17 June 2015 at the University of Ottawa, as part of PGCon 2015. This Unconference will be focused on technical PostgreSQL development discussions ranging from Clustering and replication to the infrastructure which runs postgresql.org.<br />
<br />
'''Please add your name under RSVPs if you plan to attend.'''<br />
<br />
== Topics ==<br />
<br />
Developers are asked to propose topics which they wish to either present on or which they would like another individual to present on. All topics should be clearly related to PostgreSQL development. The topic should be added to the table below and any required attendees (presumably at least the presenter, and the requester if different) listed. Other attendees of the Unconference who are interested should list themselves as Optional. Note that non-technical topics related to PostgreSQL development will be addressed during the invite-only Developer meeting, being held in advance of the Unconference. Further, the Developer Unconference is for developers of PostgreSQL and user-oriented topics are not appropriate for this venue.<br />
<br />
== Slot assignment ==<br />
<br />
Slots will be assigned based on the topic's interest among the attendees of the Unconference (the number of individuals who listed themselves as attendees). Final determination on any particular topic will be made by the Unconference organizers. Please only participate if you are confident of your attendance at the Unconference.<br />
<br />
== Venue ==<br />
<br />
These meetings will be held at the University of Ottawa. The topics selected, the schedule and the specific room assignments will be published closer to the event and will be based on the information provided here. Please direct any questions to Dave Page (dpage@pgadmin.org).<br />
<br />
== Sponsorship ==<br />
<br />
The Developer Unconference will be sponsored by Salesforce.com, and by NTT Open Source for the Clustering Track.<br />
<br />
== Attendees ==<br />
<br />
While the Unconference is open to all attendees of PGCon, formal invitations will be sent to specific PostgreSQL developers, including the Core team, Major Contributors, Committers, and other developers who have been involved in the 9.4 release. These invitations are intended to encourage developers to attend the Unconference but we are unable to guarantee every invitee a speaking slot.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname):<br />
<br />
* Ashutosh Bapat<br />
* Oleg Bartunov<br />
* Josh Berkus<br />
* Jeff Davis<br />
* Ozgun Erdogan<br />
* Andres Freund<br />
* Stephen Frost<br />
* Masao Fujii<br />
* Etsuro Fujita<br />
* Peter Geoghegan<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Ahsan Hadi<br />
* Shigeru Hanada<br />
* Álvaro Herrera<br />
* Kyotaro Horiguchi<br />
* Thierry Husson (Wednesday @ 11am)<br />
* Ayumi Ishii<br />
* Stefan Kaltenbrunner<br />
* Amit Kapila<br />
* Konstantin Knizhnik<br />
* KaiGai Kohei (arrive tuesday evening)<br />
* Alexander Korotkov<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
* Grant McAlister<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Jim Nasby<br />
* Dave Page<br />
* Magnus Hagander<br />
* Kumar Rajeev Rastogi<br />
* Simon Riggs<br />
* Tetsuo Sakata<br />
* Masahiko Sawada<br />
* Marco Slot (Wednesday)<br />
* Greg Smith<br />
* Steve Singer (arrive tuesday mid-afternoon)<br />
* Tomas Vondra<br />
* Tatsuo Ishii<br />
* Yugo Nagata<br />
* Jan Wieck (arrive tuesday evening)<br />
* Joe Conway<br />
* Naoya Anzai (arrive tuesday evening)<br />
* David Steele (arrive tuesday evening)<br />
<br />
=Topics=<br />
<br />
'''Please add any topics you wish covered to the table.'''<br />
<br />
'''For any topics you are requesting or presenting on, please add your name in the Required column.'''<br />
<br />
'''For any topics you would like to attend, please add your name in the Interested column.'''<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Topic<br />
!Policy<br />
!Taker of Notes<br />
!Required Attendees<br />
!Interested Attendees<br />
<br />
|- style="background-color:lightgray;"<br />
|pgAdmin4<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost<br />
|Magnus Hagander, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Infrastructure Q&A<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander, Joe Conway<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|WWW Team Meeting<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Advocacy Team Meeting<br />
|Open<br />
|<br />
|Stephen Frost<br />
|Magnus Hagander, Greg Smith, Jim Nasby, Josh Berkus, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Vertical Scalability w.r.t Writes<br />
|Open<br />
|Amit Kapila<br />
|Amit Kapila<br />
|Greg Smith, Hannu Valtonen, Ilya Kosmodemiansky, Tomas Vondra, Grant McAlister, Joe Conway, Kyotaro Horiguchi, Simon Riggs, Amit Langote, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Security Team Meeting<br />
|Closed<br />
|<br />
|Heikki Linnakangas, Stephen Frost, Magnus Hagander<br />
|Noah Misch, Álvaro Herrera, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Compilation + LLVM<br />
|Open<br />
|<br />
|Kumar Rajeev Rastogi<br />
|Jeff Davis, Ozgun Erdogan, Tomas Vondra, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Horizontal Scalability / Sharding in PostgreSQL]] - ground covered so far and remaining to be covered. <br />
|Open<br />
|<br />
|Ahsan Hadi, Ashutosh Bapat, Etsuro Fujita<br />
|Hannu Valtonen, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Tetsuo Sakata, SImon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PGCAC Board Meeting 2015]]<br />
|Open*<br />
|Josh Berkus<br />
|Josh Berkus, Chris Browne, Steve Singer, Dan Langille, Dave Page<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|pgPool2 towards version 3.5]]<br />
|Open<br />
|<br />
|Tatsuo Ishii<br />
|Ashutosh Bapat<br />
<br />
|- style="background-color:lightgray;"<br />
|Partitioning<br />
|Open<br />
|<br />
|Amit Langote<br />
|Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Kyotaro Horiguchi, KaiGai Kohei, Noah Misch, Tetsuo Sakata, Álvaro Herrera, Thierry Husson, Joe Conway, Naoya Anzai, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Foreign Data Wrapper enhancements]]<br />
|Open<br />
|<br />
|Shigeru Hanada, Etsuro Fujita<br />
|KaiGai Kohei, Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Noah Misch, Tetsuo Sakata, Naoya Anzai, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Utilization of modern semiconductor - GPU, SSD, NVRAM, FPGA, ...<br />
|Open<br />
|<br />
|KaiGai Kohei<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Columnar Storage<br />
|Open<br />
|<br />
|Álvaro Herrera<br />
|Ozgun Erdogan, Tomas Vondra, KaiGai Kohei, Amit Kapila, Josh Berkus, Naoya Anzai, Amit Langote, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Future of PostgreSQL shared-nothing cluster<br />
|Open<br />
|<br />
|Konstantin Knizhnik, Alexander Korotkov, Oleg Bartunov<br />
|Jeff Davis, Amit Langote, Kumar Rajeev Rastogi, Josh Berkus, Simon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PostgreSQL and SMR Drives]] - the future of magnetic storage means very expensive random writes<br />
|Open<br />
|<br />
|Jeff Davis<br />
|Kumar Rajeev Rastogi, Noah Misch, Ilya Kosmodemiansky, Amit Kapila, Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Slony Development]]<br />
|Open<br />
|<br />
| Steve Singer, Chris Browne, Jan Wieck<br />
| Josh Berkus<br />
<br />
|- style="background-color:lightgray;"<br />
|[[DockerizingPostgres|Dockerizing Postgres]]<br />
|Open<br />
|<br />
| Josh Berkus<br />
| Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[Bi Directional Replication & Logical Decoding|Bi Directional Replication & Logical Decoding|BDR]]<br />
|Open<br />
|<br />
| Simon Riggs<br />
| Andres Freund<br />
<br />
|- style="background-color:lightgray;"<br />
|Autonomous Transactions<br />
|Open<br />
|<br />
| Simon Riggs, Kumar Rajeev Rastogi<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Audit Logging<br />
|Open<br />
|<br />
| David Steele<br />
|<br />
<br />
|}<br />
<br />
== pgAdmin4 ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Infrastructure Q&A ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== WWW Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Advocacy Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Vertical Scalability w.r.t Writes ==<br />
Purpose of this discussion:<br />
* Discuss about priority/importance of various performance and scalability problems<br />
* Solution/Idea to solve most important problem('s)<br />
* Is pgbench sufficient to capture various kind of real world workloads?<br />
<br />
Some of important performance problems I have in mind are:<br />
* Avoid/Reduce Vacuum Freeze<br />
* Bloat<br />
Heap<br />
Index<br />
* Instability in TPS due to checkpointer flush<br />
* Tuple size<br />
Heap Tuple Header <br />
Alignment in index can lead to bigger index size for simple datatypes<br />
Scalability bottlenecks<br />
* Locks<br />
ProcArrayLock<br />
WALWriteLock<br />
CLOGControlLock<br />
Lock for Relation Extension<br />
<br />
* Writes, especially when data doesn't fit in shared buffers.<br />
Write Performance<br />
Double Buffering<br />
In-memory table/tablespaces<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Security Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* This will be, ehem, secure so nothing will be written here<br />
<br />
== Partitioning ==<br />
Proposal to enhance partitioning support in PostgreSQL was posted to -hackers last year and resulted in discussion of some ideas regarding implementation. Late in the discussion, a crude WIP patch was also posted with some experimental syntax, catalog changes, an idea for internal representation and a proof-of-concept INSERT tuple routing function demonstrating practicality of the internal representation. It would be nice to carry the discussion forward at the same time implementing a patch to be proposed, reviewed early in the 9.6 development cycle. Points to discuss could be: <br />
<br />
* New features and old inheritance based implementation<br />
* Planner considerations for new partitioned table<br />
* Need for a new Append-like executor node for partitioned tables<br />
* DML/DDL restrictions on partitioned tables and partitions<br />
* Basically any considerations for partitioned tables and partitions that are explicitly defined so at a layer that's above the storage layer<br />
* Other points that come up<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Utilization of modern semiconductor ==<br />
Recent evolution of semiconductor devices make us re-consider the assumption we stand on, and utilization of its power is key of innovation.<br />
We'd like to have a discussion to get the future direction in short and middle/long term.<br />
<br />
* GPU, FPGA - have advantage on simple but massive amount of calculation. It allows DBMS to perform as data processing platform that works nearby data.<br />
<br />
* SSD, NVRAM - likely, game changer of storage layer on both of read/write workloads. DBMS also has to pay attention characteristics of these devices.<br />
<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Future of PostgreSQL shared-nothing cluster ==<br />
<br />
=== Meeting Notes ===<br />
In 2015 PostgreSQL Professional company started project of migration PostgreSQL-XL to codebase of PostgreSQL 9.4 and increasing its stability and usability. At this unconference session we'd like to discuss current progress and further development. Generally we'd like to find ways to reduce difference between PostgreSQL and its shared-nothing cluster fork so that burden of the maintenance become manageable. <br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== PostgreSQL and SMR Drives ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Native Columnar Storage ==<br />
<br />
See Alvaro's [http://www.postgresql.org/message-id/20150611230316.GM133018@postgresql.org email to Hackers].<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Unconference&diff=24975PgCon 2015 Developer Unconference2015-06-12T17:37:46Z<p>Dsteele: /* RSVPs */</p>
<hr />
<div>An Unconference-style multi-track (three tracks are currently planned) event for active PostgreSQL developers will be held from the afternoon of Tuesday 16 June, 2015 through Wednesday 17 June 2015 at the University of Ottawa, as part of PGCon 2015. This Unconference will be focused on technical PostgreSQL development discussions ranging from Clustering and replication to the infrastructure which runs postgresql.org.<br />
<br />
'''Please add your name under RSVPs if you plan to attend.'''<br />
<br />
== Topics ==<br />
<br />
Developers are asked to propose topics which they wish to either present on or which they would like another individual to present on. All topics should be clearly related to PostgreSQL development. The topic should be added to the table below and any required attendees (presumably at least the presenter, and the requester if different) listed. Other attendees of the Unconference who are interested should list themselves as Optional. Note that non-technical topics related to PostgreSQL development will be addressed during the invite-only Developer meeting, being held in advance of the Unconference. Further, the Developer Unconference is for developers of PostgreSQL and user-oriented topics are not appropriate for this venue.<br />
<br />
== Slot assignment ==<br />
<br />
Slots will be assigned based on the topic's interest among the attendees of the Unconference (the number of individuals who listed themselves as attendees). Final determination on any particular topic will be made by the Unconference organizers. Please only participate if you are confident of your attendance at the Unconference.<br />
<br />
== Venue ==<br />
<br />
These meetings will be held at the University of Ottawa. The topics selected, the schedule and the specific room assignments will be published closer to the event and will be based on the information provided here. Please direct any questions to Dave Page (dpage@pgadmin.org).<br />
<br />
== Sponsorship ==<br />
<br />
The Developer Unconference will be sponsored by Salesforce.com, and by NTT Open Source for the Clustering Track.<br />
<br />
== Attendees ==<br />
<br />
While the Unconference is open to all attendees of PGCon, formal invitations will be sent to specific PostgreSQL developers, including the Core team, Major Contributors, Committers, and other developers who have been involved in the 9.4 release. These invitations are intended to encourage developers to attend the Unconference but we are unable to guarantee every invitee a speaking slot.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname):<br />
<br />
* Ashutosh Bapat<br />
* Oleg Bartunov<br />
* Josh Berkus<br />
* Jeff Davis<br />
* Ozgun Erdogan<br />
* Andres Freund<br />
* Stephen Frost<br />
* Masao Fujii<br />
* Etsuro Fujita<br />
* Peter Geoghegan<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Ahsan Hadi<br />
* Shigeru Hanada<br />
* Álvaro Herrera<br />
* Kyotaro Horiguchi<br />
* Thierry Husson (Wednesday @ 11am)<br />
* Ayumi Ishii<br />
* Stefan Kaltenbrunner<br />
* Amit Kapila<br />
* Konstantin Knizhnik<br />
* KaiGai Kohei (arrive tuesday evening)<br />
* Alexander Korotkov<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
* Grant McAlister<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Jim Nasby<br />
* Dave Page<br />
* Magnus Hagander<br />
* Kumar Rajeev Rastogi<br />
* Simon Riggs<br />
* Tetsuo Sakata<br />
* Masahiko Sawada<br />
* Marco Slot (Wednesday)<br />
* Greg Smith<br />
* Steve Singer (arrive tuesday mid-afternoon)<br />
* Tomas Vondra<br />
* Tatsuo Ishii<br />
* Yugo Nagata<br />
* Jan Wieck (arrive tuesday evening)<br />
* Joe Conway<br />
* Naoya Anzai (arrive tuesday evening)<br />
* David Steele (arrive tuesday evening)<br />
<br />
=Topics=<br />
<br />
'''Please add any topics you wish covered to the table.'''<br />
<br />
'''For any topics you are requesting or presenting on, please add your name in the Required column.'''<br />
<br />
'''For any topics you would like to attend, please add your name in the Interested column.'''<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Topic<br />
!Policy<br />
!Taker of Notes<br />
!Required Attendees<br />
!Interested Attendees<br />
<br />
|- style="background-color:lightgray;"<br />
|pgAdmin4<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost<br />
|Magnus Hagander, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Infrastructure Q&A<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander, Joe Conway<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|WWW Team Meeting<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Advocacy Team Meeting<br />
|Open<br />
|<br />
|Stephen Frost<br />
|Magnus Hagander, Greg Smith, Jim Nasby, Josh Berkus, Joe Conway<br />
<br />
|- style="background-color:lightgray;"<br />
|Vertical Scalability w.r.t Writes<br />
|Open<br />
|Amit Kapila<br />
|Amit Kapila<br />
|Greg Smith, Hannu Valtonen, Ilya Kosmodemiansky, Tomas Vondra, Grant McAlister, Joe Conway, Kyotaro Horiguchi, Simon Riggs, Amit Langote, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Security Team Meeting<br />
|Closed<br />
|<br />
|Heikki Linnakangas, Stephen Frost, Magnus Hagander<br />
|Noah Misch, Álvaro Herrera, Andres Freund, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Compilation + LLVM<br />
|Open<br />
|<br />
|Kumar Rajeev Rastogi<br />
|Jeff Davis, Ozgun Erdogan, Tomas Vondra, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Horizontal Scalability / Sharding in PostgreSQL]] - ground covered so far and remaining to be covered. <br />
|Open<br />
|<br />
|Ahsan Hadi, Ashutosh Bapat, Etsuro Fujita<br />
|Hannu Valtonen, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Tetsuo Sakata, SImon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PGCAC Board Meeting 2015]]<br />
|Open*<br />
|Josh Berkus<br />
|Josh Berkus, Chris Browne, Steve Singer, Dan Langille, Dave Page<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|pgPool2 towards version 3.5]]<br />
|Open<br />
|<br />
|Tatsuo Ishii<br />
|Ashutosh Bapat<br />
<br />
|- style="background-color:lightgray;"<br />
|Partitioning<br />
|Open<br />
|<br />
|Amit Langote<br />
|Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Kyotaro Horiguchi, KaiGai Kohei, Noah Misch, Tetsuo Sakata, Álvaro Herrera, Thierry Husson, Joe Conway, Naoya Anzai, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Foreign Data Wrapper enhancements]]<br />
|Open<br />
|<br />
|Shigeru Hanada, Etsuro Fujita<br />
|KaiGai Kohei, Hannu Valtonen, Ashutosh Bapat, Jeff Davis, Amit Langote, Kyotaro Horiguchi, Noah Misch, Tetsuo Sakata, Naoya Anzai, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Utilization of modern semiconductor - GPU, SSD, NVRAM, FPGA, ...<br />
|Open<br />
|<br />
|KaiGai Kohei<br />
|<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Columnar Storage<br />
|Open<br />
|<br />
|Álvaro Herrera<br />
|Ozgun Erdogan, Tomas Vondra, KaiGai Kohei, Amit Kapila, Josh Berkus, Naoya Anzai, Amit Langote, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|Future of PostgreSQL shared-nothing cluster<br />
|Open<br />
|<br />
|Konstantin Knizhnik, Alexander Korotkov, Oleg Bartunov<br />
|Jeff Davis, Amit Langote, Kumar Rajeev Rastogi, Josh Berkus, Simon Riggs, Robert Haas<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PostgreSQL and SMR Drives]] - the future of magnetic storage means very expensive random writes<br />
|Open<br />
|<br />
|Jeff Davis<br />
|Kumar Rajeev Rastogi, Noah Misch, Ilya Kosmodemiansky, Amit Kapila, Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Slony Development]]<br />
|Open<br />
|<br />
| Steve Singer, Chris Browne, Jan Wieck<br />
| Josh Berkus<br />
<br />
|- style="background-color:lightgray;"<br />
|[[DockerizingPostgres|Dockerizing Postgres]]<br />
|Open<br />
|<br />
| Josh Berkus<br />
| Simon Riggs<br />
<br />
|- style="background-color:lightgray;"<br />
|[[Bi Directional Replication & Logical Decoding|Bi Directional Replication & Logical Decoding|BDR]]<br />
|Open<br />
|<br />
| Simon Riggs<br />
| Andres Freund<br />
<br />
|- style="background-color:lightgray;"<br />
|Autonomous Transactions<br />
|Open<br />
|<br />
| Simon Riggs, Kumar Rajeev Rastogi<br />
|<br />
<br />
<br />
|}<br />
<br />
== pgAdmin4 ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Infrastructure Q&A ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== WWW Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Advocacy Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Vertical Scalability w.r.t Writes ==<br />
Purpose of this discussion:<br />
* Discuss about priority/importance of various performance and scalability problems<br />
* Solution/Idea to solve most important problem('s)<br />
* Is pgbench sufficient to capture various kind of real world workloads?<br />
<br />
Some of important performance problems I have in mind are:<br />
* Avoid/Reduce Vacuum Freeze<br />
* Bloat<br />
Heap<br />
Index<br />
* Instability in TPS due to checkpointer flush<br />
* Tuple size<br />
Heap Tuple Header <br />
Alignment in index can lead to bigger index size for simple datatypes<br />
Scalability bottlenecks<br />
* Locks<br />
ProcArrayLock<br />
WALWriteLock<br />
CLOGControlLock<br />
Lock for Relation Extension<br />
<br />
* Writes, especially when data doesn't fit in shared buffers.<br />
Write Performance<br />
Double Buffering<br />
In-memory table/tablespaces<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Security Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* This will be, ehem, secure so nothing will be written here<br />
<br />
== Partitioning ==<br />
Proposal to enhance partitioning support in PostgreSQL was posted to -hackers last year and resulted in discussion of some ideas regarding implementation. Late in the discussion, a crude WIP patch was also posted with some experimental syntax, catalog changes, an idea for internal representation and a proof-of-concept INSERT tuple routing function demonstrating practicality of the internal representation. It would be nice to carry the discussion forward at the same time implementing a patch to be proposed, reviewed early in the 9.6 development cycle. Points to discuss could be: <br />
<br />
* New features and old inheritance based implementation<br />
* Planner considerations for new partitioned table<br />
* Need for a new Append-like executor node for partitioned tables<br />
* DML/DDL restrictions on partitioned tables and partitions<br />
* Basically any considerations for partitioned tables and partitions that are explicitly defined so at a layer that's above the storage layer<br />
* Other points that come up<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Utilization of modern semiconductor ==<br />
Recent evolution of semiconductor devices make us re-consider the assumption we stand on, and utilization of its power is key of innovation.<br />
We'd like to have a discussion to get the future direction in short and middle/long term.<br />
<br />
* GPU, FPGA - have advantage on simple but massive amount of calculation. It allows DBMS to perform as data processing platform that works nearby data.<br />
<br />
* SSD, NVRAM - likely, game changer of storage layer on both of read/write workloads. DBMS also has to pay attention characteristics of these devices.<br />
<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Future of PostgreSQL shared-nothing cluster ==<br />
<br />
=== Meeting Notes ===<br />
In 2015 PostgreSQL Professional company started project of migration PostgreSQL-XL to codebase of PostgreSQL 9.4 and increasing its stability and usability. At this unconference session we'd like to discuss current progress and further development. Generally we'd like to find ways to reduce difference between PostgreSQL and its shared-nothing cluster fork so that burden of the maintenance become manageable. <br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== PostgreSQL and SMR Drives ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<br />
<br />
== Native Columnar Storage ==<br />
<br />
See Alvaro's [http://www.postgresql.org/message-id/20150611230316.GM133018@postgresql.org email to Hackers].<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in</div>Dsteelehttps://wiki.postgresql.org/index.php?title=Postgres_Open_2014&diff=23232Postgres Open 20142014-09-24T00:00:11Z<p>Dsteele: </p>
<hr />
<div>Conference website: [http://postgresopen.org/2014/ PostgresOpen 2014]<br />
<br />
Events shown for placeholding purposes. See the "Editing help" for instructions on how to add a link to your slides.<br />
<br />
== Wednesday September 17 (Tutorials) ==<br />
* [http://www.joeconway.com/presentations/adv_sql_and_functions.pdf Adv. SQL + Functions (Joe Conway, Stephen Frost)]<br />
* PostGIS Introduction: Geometry, Geography, and Geocoding (Regina Obe, Leo Hsu) [http://www.postgis.us/Presentations/PGOpen2014_Session1.html HTML] [http://www.postgis.us/Presentations/PGOpen2014_Session1.pdf PDF] [http://www.postgis.us/PGOpen2014 related data and docs] <br />
* PostGIS on caffeine: Raster, Topology, and pgRouting (Regina Obe, Leo Hsu) [http://www.postgis.us/Presentations/PGOpen2014_Session2.html HTML] [http://www.postgis.us/Presentations/PGOpen2014_Session2.pdf PDF] [http://www.postgis.us/PGOpen2014 related data and docs]<br />
* Writing & Using Postgres Extensions ([http://tapoueh.org/ Dimitri Fontaine]) [http://tapoueh.org/images/confs/PostgresOpen_2014_Extension.pdf PostgresOpen_2014_Extension.pdf]<br />
* Using the Heroku Platform (Free) (Harold Giménez) ([https://speakerdeck.com/hgmnz/heroku-tutorial Slides])<br />
* NoSQL on ACID (Free) (Bruce Momjian)<br />
<br />
== Thursday September 18 ==<br />
* Sponsor Keynote (Marc Linster)<br />
<br />
* [http://momjian.us/main/writings/pgsql/optimizer.pdf Explaining the Postgres Query Optimizer (Bruce Momjian)]<br />
* [http://www.slideshare.net/denishpatel/postgres-in-amazon-rds-pg-open2014dpatel Postgres in Amazon RDS (Denish Patel)]<br />
* [http://gurjeet.singh.im/presentations/HowDatabasesWorkPGOpen2014.pdf How Databases Work] - For Developers, Accidental DBAs and Managers (Gurjeet Singh)<br />
<br />
* Scalability, Consistency, Replication, Availability and Performance (Simon Riggs)<br />
* [https://wiki.postgresql.org/wiki/Postgres_Open_2014 The NoSQL Way In PostgreSQL (Vibhor Kumar)]<br />
* So you're new to Postgres... (Michael Alan Brewer)<br />
<br />
* [http://www.joeconway.com/presentations/test-pres.pdf Who's the Fairest of Them All? Postgres Interface Performance (Joe Conway)]<br />
* What's new in PostgreSQL 9.4 (Magnus Hagander)<br />
* [https://wiki.postgresql.org/wiki/File:Postgres_on_OpenStack.pdf Postgres on OpenStack (Dave Page)]<br />
<br />
* Automated Performance Testing of Postgres (Greg Burek)<br />
* Survival analysis of customer retention using Postgres, SQL and R (Gleb Arshinov)<br />
* [http://www.slideshare.net/xenophenes/talk-39404280 The Three Musketeers: Authentication, Authorization and Accounting (Sarah Conway) ] <br />
<br />
* On Beyond Data Types (Jonathan S. Katz)<br />
* Supersized Postgres: Postgres-XL for OLTP and Big Data Analytics (Mason Sharp)<br />
* [http://slides.com/danmcclain/postgresopen-2014 Use PostgreSQL, not Rails, to make Rails faster! (Dan McClain)]<br />
<br />
== Lightning Talks ==<br />
* Collations and Filesystem-based Copies (Matthew Kelly)<br />
* pgcharts (Dimitri Fontaine)<br />
* Terra Populus (David Haynes)<br />
* DDL generator (Catherine Devlin)<br />
* Is Your Bank ''Really'' on Acid? (Rob Treat)<br />
* crontabber (Peter Bengtsson)<br />
* Chelnik Update (Mark Wong)<br />
<br />
== Friday, September 19 ==<br />
<br />
* PostgreSQL Scale-Out at InMobi (Sivakumar)<br />
* Row-Estimation Revelation and the Monolithic Query Syndrome (Jeff Amiel)<br />
* Tales from the Postgres Front, and What We Can Learn (Marc Linster)<br />
<br />
* PostgreSQL for developers ([http://tapoueh.org Dimitri Fontaine]) [http://tapoueh.org/images/confs/PostgresOpen_2014_PostgreSQL_for_Developers.pdf PostgresOpen_2014_PostgreSQL_for_Developers.pdf]<br />
* Database Security and Audit Logging: User-Centered Security with JackDB (Sehrope Sarkuni)<br />
* [https://rawgit.com/garysieling/postgres-immutable-data/master/index.html Immutable Data in Postgres (Gary Sieling)]<br />
<br />
* How VACUUM works, and what to do when it doesn't (Simon Riggs)<br />
* [https://github.com/dwsteele/conference/releases/tag/HeavyDutyPgBackRest-PostgresOpen2014 Heavy Duty Backup with PgBackRest (David Steele)]<br />
* [https://www.dropbox.com/s/sgp2byhckm48izk/pgopen-2014-full-PDF.pdf Migrating away from MySQL for an awesome fulltext search] ([http://www.peterbe.com Peter Bengtsson])<br />
<br />
* PostgreSQL and Java: best practices (Álvaro Hernández)<br />
* [[Media:collectd-graphite.pdf|Collectd and Graphite: Monitoring PostgreSQL with Style]] ([http://bonesmoses.org/ Shaun Thomas])<br />
* [http://www.slideshare.net/citus_data/cstorefdw-columnar-storage-for-postgresql Columnar Store for PostgreSQL] (Ben Redman)<br />
<br />
* Row Level Security (Stephen Frost)<br />
* Holistic Database Application Tuning – Factoring UDFs in an All-new Way Grant Evans, (Henrietta Dombrovskaya)<br />
* [http://tinyurl.com/frictionless-data-science Frictionless Data Science with Python] (Catherine Devlin)<br />
* [http://michael.otacoo.com/content/materials/20140919_pgopen_logirep.pdf Understanding logical decoding and replication] ([http://michael.otacoo.com/ Michael Paquier])<br />
* A Performance Comparison of Postgres on Different Storage Systems Dong Ye, Syed (Faisal Akber)<br />
* A Quantitative Look at Partitions (john melesky)<br />
<br />
*Sponsor Keynote (Simon Riggs)</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PGConf_NYC_2014_Talks&diff=22074PGConf NYC 2014 Talks2014-04-07T10:38:05Z<p>Dsteele: /* Empire Room */</p>
<hr />
<div>= PGConf NYC 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://nyc.pgconf.us/2014<br />
<br />
== Talks: Thursday April 3, 2014 ==<br />
<br />
=== Grand Ballroom Salon A&B ===<br />
<br />
[http://nbviewer.ipython.org/gist/nyamada/9946705 Using Postgres for append-only immutable data]<br />
<br />
=== Grand Ballroom Salon C ===<br />
[https://wiki.postgresql.org/wiki/File:Achieving_PCI_Compliace_PgConfNYC2014.pdf Achieving PCI compliance with Postgres]<br />
<br />
=== Empire Room ===<br />
[https://wiki.postgresql.org/wiki/File:Pgconfnyc2014_whenpgcantyoucan.pdf When PostgreSQL Can't, You Can]<br />
<br />
== Talks: Friday April 4, 2014 ==<br />
<br />
=== Grand Ballroom Salon A&B ===<br />
<br />
=== Grand Ballroom Salon C ===<br />
<br />
=== Empire Room ===<br />
<br />
* [https://github.com/dwsteele/conference/releases/tag/release%2FDatabaseValidationAndVersioning-PGConfNYC2014 Database Validation and Versioning]<br />
* [http://www.slideshare.net/gavinmroy/integrating-postgresql-with-rabbitmq Integrating PostgreSQL with RabbitMQ]<br />
* [https://wiki.postgresql.org/wiki/File:Eav-pgconfnyc2014.pdf An Adventure in Data Modeling: The Entity-Attribute-Value Data Model]</div>Dsteelehttps://wiki.postgresql.org/index.php?title=PGConf_NYC_2014_Talks&diff=22073PGConf NYC 2014 Talks2014-04-07T10:37:41Z<p>Dsteele: </p>
<hr />
<div>= PGConf NYC 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://nyc.pgconf.us/2014<br />
<br />
== Talks: Thursday April 3, 2014 ==<br />
<br />
=== Grand Ballroom Salon A&B ===<br />
<br />
[http://nbviewer.ipython.org/gist/nyamada/9946705 Using Postgres for append-only immutable data]<br />
<br />
=== Grand Ballroom Salon C ===<br />
[https://wiki.postgresql.org/wiki/File:Achieving_PCI_Compliace_PgConfNYC2014.pdf Achieving PCI compliance with Postgres]<br />
<br />
=== Empire Room ===<br />
[https://wiki.postgresql.org/wiki/File:Pgconfnyc2014_whenpgcantyoucan.pdf When PostgreSQL Can't, You Can]<br />
<br />
== Talks: Friday April 4, 2014 ==<br />
<br />
=== Grand Ballroom Salon A&B ===<br />
<br />
=== Grand Ballroom Salon C ===<br />
<br />
=== Empire Room ===<br />
<br />
* [http://www.slideshare.net/gavinmroy/integrating-postgresql-with-rabbitmq Integrating PostgreSQL with RabbitMQ]<br />
* [https://wiki.postgresql.org/wiki/File:Eav-pgconfnyc2014.pdf An Adventure in Data Modeling: The Entity-Attribute-Value Data Model]<br />
* [https://github.com/dwsteele/conference/releases/tag/release%2FDatabaseValidationAndVersioning-PGConfNYC2014 Database Validation and Versioning]</div>Dsteele