https://wiki.postgresql.org/api.php?action=feedcontributions&user=Fuzzycz&feedformat=atomPostgreSQL wiki - User contributions [en]2024-03-29T12:52:56ZUser contributionsMediaWiki 1.35.13https://wiki.postgresql.org/index.php?title=Speaker_Bureau&diff=38529Speaker Bureau2023-12-19T10:33:02Z<p>Fuzzycz: </p>
<hr />
<div>In order to help with the challenge of finding speakers for meetups please add your name to this page if you are willing to speak at a meetup. '''At a minimum add your name, topic(s) and timezone'''. Feel free to add anything else you feel is relevant.<br />
<br />
Please use the [https://www.iana.org/time-zones IANA database] name for your time zone. For languages, English is assumed. Please use a comma-space list of [https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes ISO 639 Set 1] codes for other languages that you can deliver talks in comfortably. The space after the comma is important for help in searching for a language code.<br />
<br />
For user group organizers who'd like to contact a speaker, please email the PgUS User Group Committee (ugcomm at PostgreSQL dot us), and we'll forward the request to the speaker. <br />
<br />
{| class="wikitable sortable""<br />
|+ Speaker Bureau<br />
|-<br />
! style="width: 10em;" | Name !! Time zone !! style="width: 60em;" | Topics !! Language !! Mentor new speakers? !! Willing to travel?<br />
|-<br />
| Alicja Kucharczyk || CE(S)T || Postgres tuning, Oracle to Postgres migrations, Azure, Citus || || Yes || <br />
|-<br />
| Álvaro Herrera || Europe/Berlin || Postgres tuning, MVCC/vacuuming, Partitioning, Postgres hacking, community || || || <br />
|-<br />
| Andreas [[User:ads|ads]] Scherbaum || CE(S)T || PostgreSQL, Data Types, Community, Migration, Ansible ([https://andreas.scherbaum.la/writings/ Talks]) || || Yes || Yes<br />
|-<br />
| Andrew Dunstan || EST || PostgreSQL, vacuuming and freezing, Data Types, Foreign Data Wrappers, SSL, Pgbouncer || || || Yes<br />
|-<br />
| Ashutosh Bapat || Asia/Kolkata || PostgreSQL Architecture, distributed postgresql, logical replication, partitioning, horizontal scalability || || Yes || Yes<br />
|-<br />
| Boriss Mejías || CET || JSON, ENUM, replicationt || || || <br />
|-<br />
| Bruce Momjian || EST || PostgreSQL Administration, Extended, Internals, Performance, Project, SQL, Open Source || || Yes || Yes<br />
|-<br />
| [[User:c2main|Cédric Villemain]] || CE(S)T || PostgreSQL Architecture, High Availability, Distributed database, Extensions, Capacity planning, "IO" topics || || Yes || <br />
|-<br />
| Christophe Pettus || PST || Configuration and Tuning, Query Optimization, DBA Tasks and Mentoring, Disaster Recovery and Reliability Planning || || || <br />
|-<br />
| Daniel Westermann || CE(S)T || PostgreSQL, DBA related topics, query tuning || || Yes || <br />
|-<br />
| Dave Cramer || EST || Java and PostgreSQL, Logical Decoding || || Yes || <br />
|-<br />
| Dave Page || GMT || pgAdmin, PostgreSQL project organisation/infrastructure || || || <br />
|-<br />
| David Christensen || CST || Replication, Bucardo, CTEs. || || || <br />
|-<br />
| David Fetter || || PostgreSQL as a control plane, Fun with Foreign Data Wrappers, Hacking for Beginners || || || <br />
|-<br />
| Derk van Veen || Europe/Amsterdam || Performance for devs, HOT Upadates and fill factor, MVCC model, High Availability (and debugging), Data corruptions, Partitioning in Postgres, Why Partitioning performance can be poor || || Yes || Yes<br />
|-<br />
| Dimitri Fontaine || CE(S)T || PostgreSQL, High Availability, pg_auto_failover, pgloader, PostgreSQL for Developers, PostgreSQL Architectures in Production, Data Modeling || || Yes || <br />
|-<br />
| Elizabeth Christensen || CST || Postgres Newbies, PostGIS basics, DBA basics || || || <br />
|-<br />
| Euler Taveira || America/Sao_Paulo || Logical Replication, Extensions, Tuning, Community || || || <br />
|-<br />
| Federico Campoli || CE(S)T || PostgreSQL, DBA related topics, query tuning, pg_chameleon, patroni, disaster recovery || || Yes || <br />
|-<br />
| Gianni Ciolli || GMT || Several topics, including: Physical/Logical Replication, Backup&restore, Query optimization, Database administration || || || <br />
|-<br />
| Hari Kiran || Asia/Kolkata || PostgreSQL, Replication, Partitioning, Oracle Migration, Monitoring, DBA || || || <br />
|-<br />
| Harry Arroyo || || PostgreSQL with Laravel, Django, Java, IT Security Expert, TI Mentor, Sysadmin, FullStack Developer, Hacker, App Developer (Android and iOS), DBA and other Stuff || || || <br />
|-<br />
| Ilya Kosmodemiansky || CET || Community, Latest in Postgres, Linux internals, Optimisation || English, German || Yes || Yes<br />
|-<br />
| [[User:Johnnyq72|Jan Karremans]] || CE(S)T || Most topics, including Architecture, HA, Postgres in Kubernetes, PostgreSQL use-cases, Proprietary vs. PostgreSQL, PostgreSQL history and extensibility || || Yes || Yes<br />
|-<br />
| Jennifer Scheuerell || PST || Migrations, PostgreSQL and Django || || Yes || <br />
|-<br />
| Jimmy Angelakos || GMT || PostgreSQL (performance, best practices, DBA), Full-Text Search, ETL with Python, Django || || Yes || Yes<br />
|-<br />
| Joe Conway || EST || Security (variety of subtopics), Analytics (using PL/R, PostGIS, Python), Functions, Text Search and Pattern Matching, Shell Scripting with Postgres, Postgres Intro, Community and Development || || Yes || <br />
|-<br />
| Jonathan Katz || EST || SCRAM, PostgreSQL + Kubernetes, PostgreSQL 13, Range Types + Applications, Building an App with a bunch of Postgres features (Logical decoding, CTEs, functions, range types, etc.), Data Types || || || <br />
|-<br />
| Karen Jex || CET || PostgreSQL, Kubernetes, DBA roles, Oracle topics, Multitenancy, Postgres arts and crafts || || Yes || <br />
|-<br />
| Keith Fiske || || Partitioning, Extensions, Administration, PG History & Features, Monitoring || || || <br />
|-<br />
| Luigi Nardi || CET || Machine Learning, Artificial Intelligence, PostgreSQL Performance, Parameter Tuning, Self-tuning Databases, Autotuning, Cloud Spend Optimization || || || <br />
|-<br />
| Lætitia Avrot || CE(S)T || PostgreSQL, Postgres Women, psql, BDR || || Yes || <br />
|-<br />
| Martín Marqués || America/Argentina/Buenos_Aires || PostgreSQL, replication, backups, autovacuum || || || <br />
|-<br />
| Muhammad Haroon || Asia/Karachi || PostgreSQL, High Availability, Logical Replication, Vacuum/AutoVacuum, Database Administration, Extensions, Disaster Recovery || || || <br />
|-<br />
| Nikhil Sontakke || Asia/Kolkata || PostgreSQL Architecture, Logical Decoding, BDR, PGLogical || || || <br />
|-<br />
| Pavan Deolasee || Asia/Kolkata || PostgreSQL Internals, Transaction Management, Performance, BDR || || || <br />
|-<br />
| [[User:Rmello|Roberto Mello]] || America/Mountain || Postgres Intro, Community and Development, Kubernetes, DBA roles, Security (intro and subtopics), Python, Multitenancy, Migration || English, Portuguese, Spanish || Yes || Yes<br />
|-<br />
| Sameer Malik || PST || PostgreSQL, Oracle, migration || || Yes || <br />
|-<br />
| [[User:Stefan.fercot|Stefan Fercot]] || Europe/Brussels || pgBackRest, PostgreSQL backups, replication, high availability || English, French || Yes || Yes<br />
|-<br />
| Stephen Frost || America/New_York || Security, PostgreSQL, other stuff || || || <br />
|-<br />
| Tom Kincaid || EST || High Availability, Deploying at Scale, MVCC, Partitioning, Performance Tuning || || || <br />
|-<br />
| Tomas Vondra || Europe/Prague || PostgreSQL, performance, benchmarking, various extensions, hacking, community stuff || English, Czech || Yes || Yes<br />
|-<br />
| Umair Shahid || GMT+5 || PostgreSQL use cases, licensing, clustering || || Yes || <br />
|-<br />
| Vibhor Kumar || EDT || PostgreSQL Use-Cases, Performance Tuning, High Availability, Distributed Database, Extensions, PostgreSQL @Scale, MVCC, PostgreSQL Architecture, Logical Replication, Database Administration || || Yes || <br />
|-<br />
| [[User:Xocolatl|Vik Fearing]] || Europe/Paris || SQL Standard, Advanced SQL, PostgreSQL (all topics), Community and Conference organization || eo, fr || Yes || Yes<br />
|-<br />
| William Ivanski || || PostgreSQL, High Availability, BDR, Database Administration, Oracle Migration, Python || || || <br />
|}</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Speaker_Bureau&diff=38528Speaker Bureau2023-12-19T10:32:39Z<p>Fuzzycz: </p>
<hr />
<div>In order to help with the challenge of finding speakers for meetups please add your name to this page if you are willing to speak at a meetup. '''At a minimum add your name, topic(s) and timezone'''. Feel free to add anything else you feel is relevant.<br />
<br />
Please use the [https://www.iana.org/time-zones IANA database] name for your time zone. For languages, English is assumed. Please use a comma-space list of [https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes ISO 639 Set 1] codes for other languages that you can deliver talks in comfortably. The space after the comma is important for help in searching for a language code.<br />
<br />
For user group organizers who'd like to contact a speaker, please email the PgUS User Group Committee (ugcomm at PostgreSQL dot us), and we'll forward the request to the speaker. <br />
<br />
{| class="wikitable sortable""<br />
|+ Speaker Bureau<br />
|-<br />
! style="width: 10em;" | Name !! Time zone !! style="width: 60em;" | Topics !! Language !! Mentor new speakers? !! Willing to travel?<br />
|-<br />
| Alicja Kucharczyk || CE(S)T || Postgres tuning, Oracle to Postgres migrations, Azure, Citus || || Yes || <br />
|-<br />
| Álvaro Herrera || Europe/Berlin || Postgres tuning, MVCC/vacuuming, Partitioning, Postgres hacking, community || || || <br />
|-<br />
| Andreas [[User:ads|ads]] Scherbaum || CE(S)T || PostgreSQL, Data Types, Community, Migration, Ansible ([https://andreas.scherbaum.la/writings/ Talks]) || || Yes || Yes<br />
|-<br />
| Andrew Dunstan || EST || PostgreSQL, vacuuming and freezing, Data Types, Foreign Data Wrappers, SSL, Pgbouncer || || || Yes<br />
|-<br />
| Ashutosh Bapat || Asia/Kolkata || PostgreSQL Architecture, distributed postgresql, logical replication, partitioning, horizontal scalability || || Yes || Yes<br />
|-<br />
| Boriss Mejías || CET || JSON, ENUM, replicationt || || || <br />
|-<br />
| Bruce Momjian || EST || PostgreSQL Administration, Extended, Internals, Performance, Project, SQL, Open Source || || Yes || Yes<br />
|-<br />
| [[User:c2main|Cédric Villemain]] || CE(S)T || PostgreSQL Architecture, High Availability, Distributed database, Extensions, Capacity planning, "IO" topics || || Yes || <br />
|-<br />
| Christophe Pettus || PST || Configuration and Tuning, Query Optimization, DBA Tasks and Mentoring, Disaster Recovery and Reliability Planning || || || <br />
|-<br />
| Daniel Westermann || CE(S)T || PostgreSQL, DBA related topics, query tuning || || Yes || <br />
|-<br />
| Dave Cramer || EST || Java and PostgreSQL, Logical Decoding || || Yes || <br />
|-<br />
| Dave Page || GMT || pgAdmin, PostgreSQL project organisation/infrastructure || || || <br />
|-<br />
| David Christensen || CST || Replication, Bucardo, CTEs. || || || <br />
|-<br />
| David Fetter || || PostgreSQL as a control plane, Fun with Foreign Data Wrappers, Hacking for Beginners || || || <br />
|-<br />
| Derk van Veen || Europe/Amsterdam || Performance for devs, HOT Upadates and fill factor, MVCC model, High Availability (and debugging), Data corruptions, Partitioning in Postgres, Why Partitioning performance can be poor || || Yes || Yes<br />
|-<br />
| Dimitri Fontaine || CE(S)T || PostgreSQL, High Availability, pg_auto_failover, pgloader, PostgreSQL for Developers, PostgreSQL Architectures in Production, Data Modeling || || Yes || <br />
|-<br />
| Elizabeth Christensen || CST || Postgres Newbies, PostGIS basics, DBA basics || || || <br />
|-<br />
| Euler Taveira || America/Sao_Paulo || Logical Replication, Extensions, Tuning, Community || || || <br />
|-<br />
| Federico Campoli || CE(S)T || PostgreSQL, DBA related topics, query tuning, pg_chameleon, patroni, disaster recovery || || Yes || <br />
|-<br />
| Gianni Ciolli || GMT || Several topics, including: Physical/Logical Replication, Backup&restore, Query optimization, Database administration || || || <br />
|-<br />
| Hari Kiran || Asia/Kolkata || PostgreSQL, Replication, Partitioning, Oracle Migration, Monitoring, DBA || || || <br />
|-<br />
| Harry Arroyo || || PostgreSQL with Laravel, Django, Java, IT Security Expert, TI Mentor, Sysadmin, FullStack Developer, Hacker, App Developer (Android and iOS), DBA and other Stuff || || || <br />
|-<br />
| Ilya Kosmodemiansky || CET || Community, Latest in Postgres, Linux internals, Optimisation || English, German || Yes || Yes<br />
|-<br />
| [[User:Johnnyq72|Jan Karremans]] || CE(S)T || Most topics, including Architecture, HA, Postgres in Kubernetes, PostgreSQL use-cases, Proprietary vs. PostgreSQL, PostgreSQL history and extensibility || || Yes || Yes<br />
|-<br />
| Jennifer Scheuerell || PST || Migrations, PostgreSQL and Django || || Yes || <br />
|-<br />
| Jimmy Angelakos || GMT || PostgreSQL (performance, best practices, DBA), Full-Text Search, ETL with Python, Django || || Yes || Yes<br />
|-<br />
| Joe Conway || EST || Security (variety of subtopics), Analytics (using PL/R, PostGIS, Python), Functions, Text Search and Pattern Matching, Shell Scripting with Postgres, Postgres Intro, Community and Development || || Yes || <br />
|-<br />
| Jonathan Katz || EST || SCRAM, PostgreSQL + Kubernetes, PostgreSQL 13, Range Types + Applications, Building an App with a bunch of Postgres features (Logical decoding, CTEs, functions, range types, etc.), Data Types || || || <br />
|-<br />
| Karen Jex || CET || PostgreSQL, Kubernetes, DBA roles, Oracle topics, Multitenancy, Postgres arts and crafts || || Yes || <br />
|-<br />
| Keith Fiske || || Partitioning, Extensions, Administration, PG History & Features, Monitoring || || || <br />
|-<br />
| Luigi Nardi || CET || Machine Learning, Artificial Intelligence, PostgreSQL Performance, Parameter Tuning, Self-tuning Databases, Autotuning, Cloud Spend Optimization || || || <br />
|-<br />
| Lætitia Avrot || CE(S)T || PostgreSQL, Postgres Women, psql, BDR || || Yes || <br />
|-<br />
| Martín Marqués || America/Argentina/Buenos_Aires || PostgreSQL, replication, backups, autovacuum || || || <br />
|-<br />
| Muhammad Haroon || Asia/Karachi || PostgreSQL, High Availability, Logical Replication, Vacuum/AutoVacuum, Database Administration, Extensions, Disaster Recovery || || || <br />
|-<br />
| Nikhil Sontakke || Asia/Kolkata || PostgreSQL Architecture, Logical Decoding, BDR, PGLogical || || || <br />
|-<br />
| Pavan Deolasee || Asia/Kolkata || PostgreSQL Internals, Transaction Management, Performance, BDR || || || <br />
|-<br />
| [[User:Rmello|Roberto Mello]] || America/Mountain || Postgres Intro, Community and Development, Kubernetes, DBA roles, Security (intro and subtopics), Python, Multitenancy, Migration || English, Portuguese, Spanish || Yes || Yes<br />
|-<br />
| Sameer Malik || PST || PostgreSQL, Oracle, migration || || Yes || <br />
|-<br />
| [[User:Stefan.fercot|Stefan Fercot]] || Europe/Brussels || pgBackRest, PostgreSQL backups, replication, high availability || English, French || Yes || Yes<br />
|-<br />
| Stephen Frost || America/New_York || Security, PostgreSQL, other stuff || || || <br />
|-<br />
| Tom Kincaid || EST || High Availability, Deploying at Scale, MVCC, Partitioning, Performance Tuning || || || <br />
|-<br />
| Tomas Vondra || CET || PostgreSQL, performance, benchmarking, various extensions, hacking, community stuff || English, Czech || Yes || Yes<br />
|-<br />
| Umair Shahid || GMT+5 || PostgreSQL use cases, licensing, clustering || || Yes || <br />
|-<br />
| Vibhor Kumar || EDT || PostgreSQL Use-Cases, Performance Tuning, High Availability, Distributed Database, Extensions, PostgreSQL @Scale, MVCC, PostgreSQL Architecture, Logical Replication, Database Administration || || Yes || <br />
|-<br />
| [[User:Xocolatl|Vik Fearing]] || Europe/Paris || SQL Standard, Advanced SQL, PostgreSQL (all topics), Community and Conference organization || eo, fr || Yes || Yes<br />
|-<br />
| William Ivanski || || PostgreSQL, High Availability, BDR, Database Administration, Oracle Migration, Python || || || <br />
|}</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Speaker_Bureau&diff=38527Speaker Bureau2023-12-19T10:31:34Z<p>Fuzzycz: </p>
<hr />
<div>In order to help with the challenge of finding speakers for meetups please add your name to this page if you are willing to speak at a meetup. '''At a minimum add your name, topic(s) and timezone'''. Feel free to add anything else you feel is relevant.<br />
<br />
Please use the [https://www.iana.org/time-zones IANA database] name for your time zone. For languages, English is assumed. Please use a comma-space list of [https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes ISO 639 Set 1] codes for other languages that you can deliver talks in comfortably. The space after the comma is important for help in searching for a language code.<br />
<br />
For user group organizers who'd like to contact a speaker, please email the PgUS User Group Committee (ugcomm at PostgreSQL dot us), and we'll forward the request to the speaker. <br />
<br />
{| class="wikitable sortable""<br />
|+ Speaker Bureau<br />
|-<br />
! style="width: 10em;" | Name !! Time zone !! style="width: 60em;" | Topics !! Language !! Mentor new speakers? !! Willing to travel?<br />
|-<br />
| Alicja Kucharczyk || CE(S)T || Postgres tuning, Oracle to Postgres migrations, Azure, Citus || || Yes || <br />
|-<br />
| Álvaro Herrera || Europe/Berlin || Postgres tuning, MVCC/vacuuming, Partitioning, Postgres hacking, community || || || <br />
|-<br />
| Andreas [[User:ads|ads]] Scherbaum || CE(S)T || PostgreSQL, Data Types, Community, Migration, Ansible ([https://andreas.scherbaum.la/writings/ Talks]) || || Yes || Yes<br />
|-<br />
| Andrew Dunstan || EST || PostgreSQL, vacuuming and freezing, Data Types, Foreign Data Wrappers, SSL, Pgbouncer || || || Yes<br />
|-<br />
| Ashutosh Bapat || Asia/Kolkata || PostgreSQL Architecture, distributed postgresql, logical replication, partitioning, horizontal scalability || || Yes || Yes<br />
|-<br />
| Boriss Mejías || CET || JSON, ENUM, replicationt || || || <br />
|-<br />
| Bruce Momjian || EST || PostgreSQL Administration, Extended, Internals, Performance, Project, SQL, Open Source || || Yes || Yes<br />
|-<br />
| [[User:c2main|Cédric Villemain]] || CE(S)T || PostgreSQL Architecture, High Availability, Distributed database, Extensions, Capacity planning, "IO" topics || || Yes || <br />
|-<br />
| Christophe Pettus || PST || Configuration and Tuning, Query Optimization, DBA Tasks and Mentoring, Disaster Recovery and Reliability Planning || || || <br />
|-<br />
| Daniel Westermann || CE(S)T || PostgreSQL, DBA related topics, query tuning || || Yes || <br />
|-<br />
| Dave Cramer || EST || Java and PostgreSQL, Logical Decoding || || Yes || <br />
|-<br />
| Dave Page || GMT || pgAdmin, PostgreSQL project organisation/infrastructure || || || <br />
|-<br />
| David Christensen || CST || Replication, Bucardo, CTEs. || || || <br />
|-<br />
| David Fetter || || PostgreSQL as a control plane, Fun with Foreign Data Wrappers, Hacking for Beginners || || || <br />
|-<br />
| Derk van Veen || Europe/Amsterdam || Performance for devs, HOT Upadates and fill factor, MVCC model, High Availability (and debugging), Data corruptions, Partitioning in Postgres, Why Partitioning performance can be poor || || Yes || Yes<br />
|-<br />
| Dimitri Fontaine || CE(S)T || PostgreSQL, High Availability, pg_auto_failover, pgloader, PostgreSQL for Developers, PostgreSQL Architectures in Production, Data Modeling || || Yes || <br />
|-<br />
| Elizabeth Christensen || CST || Postgres Newbies, PostGIS basics, DBA basics || || || <br />
|-<br />
| Euler Taveira || America/Sao_Paulo || Logical Replication, Extensions, Tuning, Community || || || <br />
|-<br />
| Federico Campoli || CE(S)T || PostgreSQL, DBA related topics, query tuning, pg_chameleon, patroni, disaster recovery || || Yes || <br />
|-<br />
| Gianni Ciolli || GMT || Several topics, including: Physical/Logical Replication, Backup&restore, Query optimization, Database administration || || || <br />
|-<br />
| Hari Kiran || Asia/Kolkata || PostgreSQL, Replication, Partitioning, Oracle Migration, Monitoring, DBA || || || <br />
|-<br />
| Harry Arroyo || || PostgreSQL with Laravel, Django, Java, IT Security Expert, TI Mentor, Sysadmin, FullStack Developer, Hacker, App Developer (Android and iOS), DBA and other Stuff || || || <br />
|-<br />
| Ilya Kosmodemiansky || CET || Community, Latest in Postgres, Linux internals, Optimisation || English, German || Yes || Yes<br />
|-<br />
| [[User:Johnnyq72|Jan Karremans]] || CE(S)T || Most topics, including Architecture, HA, Postgres in Kubernetes, PostgreSQL use-cases, Proprietary vs. PostgreSQL, PostgreSQL history and extensibility || || Yes || Yes<br />
|-<br />
| Jennifer Scheuerell || PST || Migrations, PostgreSQL and Django || || Yes || <br />
|-<br />
| Jimmy Angelakos || GMT || PostgreSQL (performance, best practices, DBA), Full-Text Search, ETL with Python, Django || || Yes || Yes<br />
|-<br />
| Joe Conway || EST || Security (variety of subtopics), Analytics (using PL/R, PostGIS, Python), Functions, Text Search and Pattern Matching, Shell Scripting with Postgres, Postgres Intro, Community and Development || || Yes || <br />
|-<br />
| Jonathan Katz || EST || SCRAM, PostgreSQL + Kubernetes, PostgreSQL 13, Range Types + Applications, Building an App with a bunch of Postgres features (Logical decoding, CTEs, functions, range types, etc.), Data Types || || || <br />
|-<br />
| Karen Jex || CET || PostgreSQL, Kubernetes, DBA roles, Oracle topics, Multitenancy, Postgres arts and crafts || || Yes || <br />
|-<br />
| Keith Fiske || || Partitioning, Extensions, Administration, PG History & Features, Monitoring || || || <br />
|-<br />
| Luigi Nardi || CET || Machine Learning, Artificial Intelligence, PostgreSQL Performance, Parameter Tuning, Self-tuning Databases, Autotuning, Cloud Spend Optimization || || || <br />
|-<br />
| Lætitia Avrot || CE(S)T || PostgreSQL, Postgres Women, psql, BDR || || Yes || <br />
|-<br />
| Martín Marqués || America/Argentina/Buenos_Aires || PostgreSQL, replication, backups, autovacuum || || || <br />
|-<br />
| Muhammad Haroon || Asia/Karachi || PostgreSQL, High Availability, Logical Replication, Vacuum/AutoVacuum, Database Administration, Extensions, Disaster Recovery || || || <br />
|-<br />
| Nikhil Sontakke || Asia/Kolkata || PostgreSQL Architecture, Logical Decoding, BDR, PGLogical || || || <br />
|-<br />
| Pavan Deolasee || Asia/Kolkata || PostgreSQL Internals, Transaction Management, Performance, BDR || || || <br />
|-<br />
| [[User:Rmello|Roberto Mello]] || America/Mountain || Postgres Intro, Community and Development, Kubernetes, DBA roles, Security (intro and subtopics), Python, Multitenancy, Migration || English, Portuguese, Spanish || Yes || Yes<br />
|-<br />
| Sameer Malik || PST || PostgreSQL, Oracle, migration || || Yes || <br />
|-<br />
| [[User:Stefan.fercot|Stefan Fercot]] || Europe/Brussels || pgBackRest, PostgreSQL backups, replication, high availability || English, French || Yes || Yes<br />
|-<br />
| Stephen Frost || America/New_York || Security, PostgreSQL, other stuff || || || <br />
|-<br />
| Tom Kincaid || EST || High Availability, Deploying at Scale, MVCC, Partitioning, Performance Tuning || || || <br />
|-<br />
| Tomas Vondra || CET || PostgreSQL, performance, benchmarking, various extensions, hacking, community stuff || English, Czech || || <br />
|-<br />
| Umair Shahid || GMT+5 || PostgreSQL use cases, licensing, clustering || || Yes || <br />
|-<br />
| Vibhor Kumar || EDT || PostgreSQL Use-Cases, Performance Tuning, High Availability, Distributed Database, Extensions, PostgreSQL @Scale, MVCC, PostgreSQL Architecture, Logical Replication, Database Administration || || Yes || <br />
|-<br />
| [[User:Xocolatl|Vik Fearing]] || Europe/Paris || SQL Standard, Advanced SQL, PostgreSQL (all topics), Community and Conference organization || eo, fr || Yes || Yes<br />
|-<br />
| William Ivanski || || PostgreSQL, High Availability, BDR, Database Administration, Oracle Migration, Python || || || <br />
|}</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Trademark_issues&diff=38102Trademark issues2023-07-31T21:27:21Z<p>Fuzzycz: add missing update from 2022/04/01</p>
<hr />
<div>The PostgreSQL community is currently battling a trademark issue with Fundación PostgreSQL. This article details the timeline of the dispute as well as various courts' findings.<br />
<br />
== Actors ==<br />
<br />
The following parties are involved in this dispute:<br />
<br />
* Core Team ([https://www.postgresql.org/developer/core/ Official Site])<br />
* Fundación PostgreSQL ([https://postgresql.fund/ Official Site])<br />
* PGCA: PostgreSQL Community Association ([https://www.postgres.ca/ Official Site])<br />
* PGEU: PostgreSQL Europe ([https://www.postgresql.eu/ Official Site])<br />
<br />
The following legal entities are presiding over this dispute:<br />
<br />
* EUIPO: European Union Intellectual Property Office ([https://euipo.europa.eu/ Official Site])<br />
* OEPM: <span lang="es">Oficina Española de Patentes y Marcas</span> ([https://oepm.es/ Official Site])<br />
* USPTO: United States Patent and Trademark Office ([https://www.uspto.gov/ Official Site])<br />
<br />
== Timeline ==<br />
<br />
* 2003-07-17, PGCA's '''POSTGRESQL''' trademark is registered in Canada (originally by PostgreSQL Inc.).<br />
* 2011-05-30, The ''PostgreSQL Community Association of Canada'' (''PGCAC'') is registered as an NPO in Canada to steward the PostgreSQL Projects assets (domain names, trademarks etc) at the request of the PostgreSQL Core Team.<br />
* 2018-04-17, PGEU's '''POSTGRESQL CONFERENCE''' trademark is registered in the EU/UK.<br />
* 2018-04-20, PGEU's '''POSTGRES CONFERENCE''' trademark is registered in the EU/UK.<br />
* 2018-08-15, PGCA's '''POSTGRES''' trademark is registered in the EU/UK.<br />
* 2018-08-15, PGCA's '''POSTGRESQL''' trademark is registered in the EU/UK.<br />
* 2018-08-15, PGCA's '''POSTGRES''' trademark is registered in the USA.<br />
* 2018-08-15, PGCA's '''POSTGRESQL''' trademark is registered in the USA.<br />
* 2020-04-27, [https://euipo.europa.eu/eSearch/#details/trademarks/W01534836 Fundación PostgreSQL registers EU trademark for '''POSTGRESQL'''] (EUIPO)<br />
* 2020-04-27, [https://euipo.europa.eu/eSearch/#details/trademarks/W01558723 Fundación PostgreSQL registers EU trademark for '''POSTGRESQL COMMUNITY'''] (EUIPO)<br />
* 2020-10-06, PGCA files EUIPO opposition for '''POSTGRESQL''' trademark<br />
* 2020-10-06, PGEU files EUIPO opposition for '''POSTGRESQL''' trademark<br />
* 2020-10-20, [http://consultas2.oepm.es/ceo/jsp/busqueda/consultaExterna.xhtml?numExp=M4089693# Fundación PostgreSQL registers Spanish trademark for '''POSTGRES'''] (OEPM)<br />
* 2020-11-20, ''Fundación PostgreSQL'' publishes blog post: [https://postgresql.fund/blog/is-it-time-to-modernize-postgresql-core/ Is it time to modernize the processes, structure and governance of the PostgreSQL Core Team?] (Fundación PostgreSQL) ([https://web.archive.org/web/*/https://postgresql.fund/blog/is-it-time-to-modernize-postgresql-core/ Archive link, including changes])<br />
* 2021-02-16, [https://euipo.europa.eu/eSearch/#details/trademarks/W01598034 Fundación PostgreSQL registers EU trademark for "POSTGRES"] (EUIPO)<br />
* 2021-03-21, PGCA files EUIPO opposition for '''POSTGRESQL COMMUNITY''' trademark<br />
* 2021-03-21, PGEU files EUIPO opposition for '''POSTGRESQL COMMUNITY''' trademark<br />
* 2021-06-25, ''Fundación PostgreSQL'' registers Spanish trademark for '''POSTGRES'''<br />
* 2021-09-13, ''Core Team'' and PGCA publish article: [https://www.postgresql.org/about/news/trademark-actions-against-the-postgresql-community-2302/ Trademark Actions Against the PostgreSQL Community] (PostgreSQL.org)<br />
* 2021-09-14, ''Fundación PostgreSQL'' publishes blog post: [https://postgresql.fund/blog/respecting-majority-questioning-status-quo-as-a-minority/ Respecting the majority, questioning the status quo as a minority] (Fundación PostgreSQL) ([https://web.archive.org/web/*/https://postgresql.fund/blog/respecting-majority-questioning-status-quo-as-a-minority/ Archive link, including changes])<br />
** This blog posting includes the following statement: "we have informed the Core Team that effective immediately Fundación PostgreSQL has unanimously passed a resolution to start the process to transfer, permanently and irrevocably, all PostgreSQL-related trademarks and domain names to the PostgreSQL Association of Canada, with no conditions or costs attached" ([https://web.archive.org/web/20210914223639/https://postgresql.fund/blog/respecting-majority-questioning-status-quo-as-a-minority/ 2021-09-14])<br />
* 2021-09-21, ''Fundación PostgreSQL'' publishes blog post: [https://postgresql.fund/blog/postgres-core-team-attacks-postgres-community/ Postgres Core Team launches unprecedented attack against the Postgres Community] (Fundación PostgreSQL) ([https://web.archive.org/web/*/https://postgresql.fund/blog/postgres-core-team-attacks-postgres-community/ Archive link, including changes])<br />
* 2021-10-20, PGCA files EUIPO opposition for '''POSTGRES''' trademark<br />
* 2021-10-20, PGEU files EUIPO opposition for '''POSTGRES''' trademark<br />
* 2022-04-12, PGCA publishes article: [https://www.postgresql.org/about/news/update-on-the-trademark-actions-against-the-postgresql-community-2437/ Update on the Trademark Actions Against the PostgreSQL Community]<br />
* 2022-06-10, ''Fundación PostgreSQL'' publishes blog post: [https://postgresql.fund/blog/re-update-on-the-trademark-actions/ Re: Update on the Trademark Actions] (Fundación PostgreSQL) ([https://web.archive.org/web/*/https://postgresql.fund/blog/re-update-on-the-trademark-actions/ Archive link, including changes])<br />
* 2022-06-23, the Spanish courts [https://www.postgres.ca/#2022-06-23 invalidate] the infringing '''POSTGRESQL''' and '''POSTGRESQL COMMUNITY''' trademark registrations.<br />
* 2022-10-05, ''Fundación PostgreSQL'' publishes blog post: [https://postgresql.fund/blog/postgres-trademarks-disagreement-proposing-a-solution/ PostgreSQL Trademarks Disagreement: Proposing a Solution] (Fundación PostgreSQL) ([https://web.archive.org/web/*/https://postgresql.fund/blog/postgres-trademarks-disagreement-proposing-a-solution/ Archive link, including changes])<br />
* 2023-05-09, The USPTO gives final rejection of ''Fundación PostgreSQL'''s '''POSTGRES''' trademark in the USA<br />
* 2023-05-09, The USPTO gives final rejection of ''Fundación PostgreSQL'''s '''POSTGRESQL''' trademark in the USA<br />
* 2023-05-09, The USPTO gives final rejection of ''Fundación PostgreSQL'''s '''POSTGRESQL COMMUNITY''' trademark in the USA<br />
* 2023-07-11, PGCA publishes article: [https://www.postgresql.org/about/news/update-on-continued-trademark-actions-against-the-postgresql-community-2673/ Update on Continued Trademark Actions Against the PostgreSQL Community] (PostgreSQL.org)<br />
* 2023-07-24, ''Fundación PostgreSQL'' publishes blog post claiming that ''PostgreSQL'' is trying to [https://postgresql.fund/blog/the-postgres-core-team-tries-to-shut-down-a-postgres-community-conference/ "shut down"] the Ibiza conference. (Fundación PostgreSQL) ([https://web.archive.org/web/*/https://postgresql.fund/blog/the-postgres-core-team-tries-to-shut-down-a-postgres-community-conference/ Archive link, including changes])<br />
* 2023-07-27, PGCA publishes article: [https://www.postgresql.org/about/news/setting-the-record-straight-more-updates-on-a-trademark-dispute-2682/ Setting the record straight: More updates on a trademark dispute] (PostgreSQL.org)<br />
<br />
== See Also ==<br />
<br />
* [https://news.ycombinator.com/item?id=28512274 Hacker News discussion]<br />
* [https://lwn.net/Articles/869108/ LWN discussion]<br />
* [https://news.ycombinator.com/item?id=36891784 Hacker News discussion]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PgCon_2023_Developer_Meeting&diff=37711PgCon 2023 Developer Meeting2023-04-07T11:08:33Z<p>Fuzzycz: </p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Tuesday 30 May, 2023 at the University of Ottawa, prior to pgCon 2023. In order to keep the numbers manageable, this meeting is by '''invitation only'''.<br />
Any questions regarding the invitations to this event should be directed to the team of individuals tasked with coming up with the list of people to invite:<br />
<br />
* Andres Freund<br />
* Stephen Frost<br />
* Dave Page<br />
<br />
An Unconference will be held on Friday 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 upcoming releases<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 (probably) be:<br />
<br />
* 9:00AM to 12PM<br />
* DMS 3105 - Desmarais Hall, 55 Laurier Avenue East<br />
* University of Ottawa.<br />
<br />
Lunch will be served during the meeting.<br />
<br />
== COVID-19 ==<br />
<br />
The University of Ottawa's COVID-19 guidance can be found at https://www.uottawa.ca/en/covid-19. Wearing of masks at the Developer Meeting will be optional, however we do ask that people do not attend if they have COVID symptoms or have tested positive.<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 />
# Peter Eisentraut<br />
# Andres Freund<br />
# Stephen Frost<br />
# Etsuro Fujita<br />
# Magnus Hagander<br />
# Jonathan Katz<br />
# Alexander Korotkov<br />
# Tom Lane<br />
# Heikki Linnakangas<br />
# Noah Misch<br />
# Thomas Munro<br />
# Dave Page<br />
# Michael Paquier<br />
# Melanie Plageman<br />
# David Rowley<br />
# Peter Geoghegan<br />
# Tomas Vondra<br />
<br />
The following people will not be in Ottawa, and do not plan to attend:<br />
<br />
# Masao Fujii<br />
# Daniel Gustafsson<br />
# Tatsuo Ishii<br />
# Dean Rasheed<br />
<br />
== Agenda Items ==<br />
<br />
* 16.0 release and commitfest schedule (Dave)<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:20<br />
|Release and commitfest schedules<br />
|Dave Page<br />
<br />
|- <br />
|??:?? - ??:??<br />
|TBD<br />
|TBD<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:30 - 11:00<br />
|Coffee break<br />
|All<br />
<br />
|- <br />
|??:?? - ??:??<br />
|TBD<br />
|TBD<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 materially however). Any remaining time before lunch may be used for Commitfest item triage or other activities.<br />
<br />
[[Category:Developer Meeting]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=36267PostgreSQL 14 Open Items2021-07-26T15:45:22Z<p>Fuzzycz: /* resolved before 14beta3 */</p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/17061-dd7f4825b7da3a9d%40postgresql.org SEARCH BREADTH FIRST produces a composite column whose fields can't be accessed]<br />
** Owner: Peter Eisentraut<br />
<br />
* [https://www.postgresql.org/message-id/17066-16a37f6223a8470b@postgresql.org Cache lookup failed when null (unknown) is passed as anycompatiblemultirange]<br />
** Owner: Alexander Korotkov<br />
<br />
* [https://www.postgresql.org/message-id/TYAPR01MB5866BA57688DF2770E2F95C6F5069@TYAPR01MB5866.jpnprd01.prod.outlook.com DECLARE STATEMENT and DEALLOCATE/DESCRIBE]<br />
** Owner: Michael Meskes<br />
<br />
* [https://www.postgresql.org/message-id/b5146fb1-ad9e-7d6e-f980-98ed68744a7c%40amazon.com Logical Decoding of relation rewrite with toast does not reset toast_hash]<br />
** Owner: Amit Kapila<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/E1lS8LX-0005sr-FZ%40gemulon.postgresql.org default setting of enable_resultcache]<br />
** Owner: David Rowley<br />
<br />
* [https://www.postgresql.org/message-id/4170264.1620321747%40sss.pgh.pa.us Should we undo libpq change that leaves PQerrorMessage() nonempty after successful connect?]<br />
** Owner: Tom Lane<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201016135230.GA23633%40alvherre.pgsql CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers]<br />
** tgenabled lost on CREATE TABLE .. PARTITION OF, and on pg_dump, and comments on child triggers lost during pg_dump;<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEudQAoR5e7=uMZ0otzuCVb25zTC8QQBe+2Dt1JRsa3u+XuwJg@mail.gmail.com could not rename temporary statistics file on Windows]<br />
** See {{PgCommitURL|909b449e00fc2f71e1a38569bbddbb6457d28485}} that has fixed a similar symptom for WAL segments. Most reporters of the WAL segment problem complained about this renaming issue as well.<br />
<br />
* [https://www.postgresql.org/message-id/20210422203603.fdnh3fu2mmfp2iov@alap3.anarazel.de Incorrect snapshot calculation when 2PC is in use]<br />
** Seems to be an old problem.<br />
<br />
* [https://www.postgresql.org/message-id/2591376.1621196582%40sss.pgh.pa.us snapshot-scalability logic fails after pg_upgrade, due to pg_resetwal issue]<br />
** Now seems likely that this is an old issue affecting every release, and that the snapshot-scalability work is not at fault<br />
** [https://commitfest.postgresql.org/33/3105/ Pending fix for pg_upgrade + pg_resetwal]<br />
** Owner: Bruce Momjian<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/trinity-1c565d44-159f-488b-a518-caf13883134f-1611835701633%403c-app-gmx-bap78 hashagg broken by failing to spill grouping columns]<br />
** Fixed at: {{PgCommitURL|0ff865fbe50e82f17df8a9280fa01faf270b7f3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAE-ML+_EjH_fzfq1F3RJ1=XaaNG=-Jz-i3JqkNhXiLAsM3z-Ew@mail.gmail.com PITR promote bug: Checkpointer writes to older timeline]<br />
** Fixed at: {{PgCommitURL|595b9cba2ab0cdd057e02d3c23f34a8bcfd90a2d}}<br />
<br />
* [https://www.postgresql.org/message-id/YFBcRbnBiPdGZvfW%40paquier.xyz Permission failures with WAL files in 13~ on Windows]<br />
** Fixed at: {{PgCommitURL|78c24e97dd189f62187a99ef84016d0eb35a7978}}<br />
<br />
* [https://www.postgresql.org/message-id/CANiYTQsU7yMFpQYnv=BrcRVqK_3U3mtAzAsJCaqtzsDHfsUbdQ@mail.gmail.com CLOBBER_CACHE Server crashed with segfault 11 while executing clusterdb]<br />
** Fixed at: {{PgCommitURL|9d523119fd38fd205cb9c8ea8e7cceeb54355818}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAV6ZkQRCVBh8qAY+SZiHnz+U+FqAGBBDaDTjF2yiKa2nJSLKg@mail.gmail.com Reference leak with tupledescs in plpgsql simple expressions]<br />
** Fixed at: {{PgCommitURL|c2db458c1036efae503ce5e451f8369e64c99541}}<br />
<br />
* [https://www.postgresql.org/message-id/a3be61d9-f44b-7fce-3dc8-d700fdfb6f48%402ndquadrant.com extract(julian) is undocumented and gives wrong result]<br />
** Fixed by documentation change at: {{PgCommitURL|79a5928ebcb726b7061bf265b5c6990e835e8c4f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGRY4nwxKUS_RvXFW-ugrZBYxPFFM5kjwKT5O+0+Stuga5b4+Q@mail.gmail.com lwlock dtrace probes do unnecessary work if dtrace is compiled in but disabled]<br />
** Fixed at: {{PgCommitURL|b94409a02f6122d77b5154e481c0819fed6b4c95}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/15990-eee2ac466b11293d%40postgresql.org Detoast failures after commit/rollback in plpgsql]<br />
** Fixed at: {{PgCommitURL|f21fadafaf0fb5ea4c9622d915972651273d62ce}} and {{PgCommitURL|84f5c2908dad81e8622b0406beea580e40bb03ac}}<br />
<br />
* [https://www.postgresql.org/message-id/3382681.1621381328%40sss.pgh.pa.us Subscription tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|b39630fd41f25b414d0ea9b30804f4105f2a0aff}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/534fca83789c4a378c7de379e9067d4f%40politie.nl XX000: unknown type of jsonb container.]<br />
** Fixed at: {{PgCommitURL|6ee41a301e70fc8e4ad383bad22d695f66ccb0ac}}<br />
<br />
* [https://www.postgresql.org/message-id/1884374.1617898865%40sss.pgh.pa.us Buildfarm does not test pg_stat_statements]<br />
** Fixed by buildfarm client change<br />
<br />
* [https://www.postgresql.org/message-id/17064-bb0d7904ef72add3%40postgresql.org Parallel VACUUM operations cause the error "global/pg_filenode.map contains incorrect checksum"]<br />
** Fixed at: {{PgCommitURL|b6d8d207}} and {{PgCommitURL|9b8ed0f52}}<br />
<br />
* [https://www.postgresql.org/message-id/378885e4-f85f-fc28-6c91-c4d1c080bf26%40amazon.com Assertion failure in HEAD and 13 after calling COMMIT in a stored proc]<br />
** Fixed at: {{PgCommitURL|d102aafb6259a6a412803d4b1d8c4f00aa17f67e}}<br />
<br />
* [https://www.postgresql.org/message-id/4aa370cb91ecf2f9885d98b80ad1109c%40postgrespro.ru Add PortalDrop in exec_execute_message]<br />
** Fixed at: {{PgCommitURL|bb4aed46a}} and {{PgCommitURL|4efcf47053}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20210216064214.GI28165%40telsasoft.com progress reporting for partitioned REINDEX]<br />
* [https://www.postgresql.org/message-id/YFnWBYinNf1s0Y6v@msg.df7cb.de pg_regress and tablespace removal]<br />
** [https://www.postgresql.org/message-id/YG/tf6HTZFj4hWlb@paquier.xyz Some patch]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 14beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/20210530172418.GO2082%40telsasoft.com#d6544e507234cc76b9bc0a50026cd74b \dX doesn't check pg_statistics_obj_is_visible()]<br />
** Fixed at: {{PgCommitURL|f68b609230689f9886a46e5d9ab8d6cdd947e0dc}}<br />
<br />
* [https://www.postgresql.org/message-id/e1b4f05d-54ec-4f51-832b-c18cf5a161c0@www.fastmail.com remove_temp_files_after_crash should be a DEVELOPER GUC]<br />
** Fixed at: {{PgCommitURL|797b0fc0b078c7b4c46ef9f2d9e47aa2d98c6c63}}<br />
<br />
* [https://www.postgresql.org/message-id/20210526001359.GE3676@telsasoft.com recovery_init_sync_method should be PGC_SIGHUP?]<br />
** Fixed at: {{PgCommitURL|34a8b64b4e5f0cd818e5cc7f98846de57938ea57}}<br />
<br />
* [https://www.postgresql.org/message-id/YNZ2mnsbDVJQrA/a@paquier.xyz OOM on palloc() when parsing service file would cause libpq to exit() without reporting a failure]<br />
** Fixed at: {{PgCommitURL|8ec00dc5cd70e0e579e9fbf8661bc46f5ccd8078}}<br />
** Additional defenses added at: {{PgCommitURL|dc227eb82ea8bf6919cd81a182a084589ddce7f3}}<br />
<br />
* [https://www.postgresql.org/message-id/17076-89a16ae835d329b9%40postgresql.org incorrect code for reporting the hash partition associated with a particular modulus]<br />
** Fixed at: {{PgCommitURL|dd2364ced98553e0217bfe8f621cd4b0970db74a}}<br />
<br />
* [https://www.postgresql.org/message-id/c5269c65-f967-77c5-ff7c-15e621c47f6a%40gmail.com Bug in multirange selectivity estimation]<br />
** Fixed at: {{PgCommitURL|322e82b77ef4acb9697c6e4259292f5671cb85bb}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/704fb6fb99ec9864a4dbeda2478337d2%40postgrespro.ru autoanalyze of partitioned table causes it to lose its relhasindex]<br />
** Fixed at: {{PgCommitURL|d700518d744e53994fdded14b23ebc15b031b0dd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAF7igB1r6wRfSCEAB-iZBKxkowWY6+dFF2jObSdd9+iVK+vHJg@mail.gmail.com Incorrect time maths in pgbench] and [https://www.postgresql.org/message-id/CAHLJuCW_8Vpcr0=t6O_gozrg3wXXWXZXDioYJd3NhvKriqgpfQ@mail.gmail.com second thread]<br />
** Fixed at: {{PgCommitURL|0e39a608ed5545cc6b9d538ac937c3c1ee8cdc36}}<br />
<br />
* [https://www.postgresql.org/message-id/60258efe-bd7e-4886-82e1-196e0cac5433%40postgresql.org unnesting multirange data types]<br />
** Fixed at: {{PgCommitURL|244ad5415557812a6ac4dc5d6e2ae908361d82c3}}<br />
<br />
=== resolved before 14beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/20210609184506.rqm5rikoikm47csf%40alap3.anarazel.de Snapshot scalability OldestXmin issue (can cause infinite loop during system catalog VACUUM)]<br />
** Fixed at: {{PgCommitURL|5a1e1d83022b976ebdec5cfa8f255c4278b75b8e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkCYR0U7zXqXo0CgFaFwUDz1WbKq8ngjzKi4+AQ5f-mYQ@mail.gmail.com Generalize INDEX_CLEANUP to allow the user to disable the optimization that has VACUUM skip indexes in marginal cases with very few LP_DEAD items/deletable TIDs.]<br />
** Fixed at: {{PgCommitURL|3499df0dee8c4ea51d264a674df5b5e31991319a}}<br />
<br />
* [https://www.postgresql.org/message-id/20210324232224.vrfiij2rxxwqqjjb@alap3.anarazel.de Questions about pg_stat_wal] also [https://www.postgresql.org/message-id/E3774ACD-7894-451E-9F13-71E097D10595@oss.nttdata.com]<br />
** Fixed at: {{PgCommitURL|d8735b8b4651f5ed50afc472e236a8e6120f07f2}}<br />
** Fixed at: {{PgCommitURL|d780d7c0882fe9a385102b292907baaceb505ed0}}<br />
<br />
* [https://www.postgresql.org/message-id/YKMO%2B2gD8R8I2O5b%40paquier.xyz pg_dumpall misses --no-toast-compression]<br />
** Fixed at: {{PgCommitURL|694da1983e9569b2a2f96cd786ead6b8dba31f1d}} <br />
<br />
* [https://www.postgresql.org/message-id/YKQnUoYV63GRJBDD%40msg.df7cb.de portability issue with pgbench's permute() function]<br />
** Fixed at: {{PgCommitURL|0f516d039d8023163e82fa51104052306068dd69}}<br />
<br />
* [https://www.postgresql.org/message-id/35457b09-36f8-add3-1d07-6034fa585ca8@oss.nttdata.com compute_query_id and pg_stat_statements]<br />
** Fixed at {{PgCommitURL|cafde58b33}} and {{PgCommitURL|354f32d01d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAOxo6X+dy-V58iEPFgst8ahPKEU+38NZzUuc+a7wDBZd4TrHMQ@mail.gmail.com Result Cache works incorrectly with unique joins]<br />
** Fixed at {{PgCommitURL|9e215378d7fbb7d4615be917917c52f246cc6c61}}<br />
<br />
* [https://www.postgresql.org/message-id/20210517204803.iyk5wwvwgtjcmc5w%40alap3.anarazel.de Move pg_attribute.attcompression to earlier in struct for reduced size?]<br />
** Fixed at {{PgCommitURL|f5024d8d7b04de2f5f4742ab433cc38160354861}}<br />
<br />
* [https://www.postgresql.org/message-id/17030-5844aecae42fe223@postgresql.org EXPLAIN can suffer from cannot decompile join alias var in plan tree]<br />
** Fixed at {{PgCommitURL|cba5c70b956810c61b3778f7041f92fbb8065acb}}<br />
<br />
* [https://www.postgresql.org/message-id/20210521211929.pcehg6f23icwstdb@alap3.anarazel.de Memory leak when rewriting tuples with recompressed toast values]<br />
** Fixed at {{PgCommitURL|fb0f5f0172edf9f63c8f70ea9c1ec043b61c770e}}<br />
<br />
* [https://www.postgresql.org/message-id/626613.1621787110%40sss.pgh.pa.us Redefine pg_attribute.attcompression]<br />
** Fixed at {{PgCommitURL|e6241d8e030fbd2746b3ea3f44e728224298f35b}}<br />
<br />
* [https://www.postgresql.org/message-id/1665197.1622065382%40sss.pgh.pa.us Undo bump of FirstBootstrapObjectId]<br />
** Fixed at {{PgCommitURL|a4390abecf0f5152cff864e82b67e5f6c8489698}}<br />
<br />
* [https://www.postgresql.org/message-id/CABOikdN-_858zojYN-2tNcHiVTw-nhxPwoQS4quExeweQfG1Ug%40mail.gmail.com Assertion failure while streaming toasted data]<br />
** Fixed at {{PgCommitURL|6f4bdf81529fdaf6744875b0be99ecb9bfb3b7e0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/7817fb9ebd6661cdf9b67dec6e129a78%40postgrespro.ru Join pushdown issue in postgres_fdw updates]<br />
** Fixed at {{PgCommitURL|f61db909dfb94f3411f8719916601a11a905b95e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoA%3D%3Df2VSw3c-Cp_y%3DWLKHMKc1D6s7g3YWsCOvgaYPpJcg%40mail.gmail.com Performance degradation of REFRESH MATERIALIZED VIEW]<br />
** Fixed at {{PgCommitURL|8e03eb92e9ad54e2f1ed8b5a73617601f6262f81}}<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK16Q4B2_KY%2BJH7rb7wQbw54AUprp7TMekGTd2T1B62yysQ%40mail.gmail.com Rescan of async Appends is broken when do_exec_prune=false]<br />
** Fixed at {{PgCommitURL|f3baaf28a6da588987b94a05a725894805c3eae9}}<br />
<br />
* [https://www.postgresql.org/message-id/504c276ab6eee000bb23d571ea9b0ced4250774e.camel%40vmware.com libpq dumps core while making an SSL connection to a server specified by hostaddr]<br />
** Fixed at {{PgCommitURL|37e1cce4ddf0be362e3093cee55493aee41bc423}}<br />
<br />
* [https://www.postgresql.org/message-id/B4A3AF82-79ED-4F4C-A4E5-CD2622098972%40enterprisedb.com logical replication of truncate command with trigger causes Assert]<br />
** Fixed at {{PgCommitURL|3a09d75b4f6cabc8331e228b6988dbfcd9afdfbe}}<br />
<br />
* [https://www.postgresql.org/message-id/3742981.1621533210%40sss.pgh.pa.us Reconsider catalog representation and uniqueness rules for procedures with output-only arguments]<br />
** Fixed at {{PgCommitURL|e56bce5d43789cce95d099554ae9593ada92b3b7}}<br />
<br />
* [https://www.postgresql.org/message-id/20210527003144.xxqppojoiwurc2iz@alap3.anarazel.de Performance regression of VACUUM FULL with the addition of recompression path in tuple rewrite]<br />
** Fixed at {{PgCommitURL|dbab0c07e5ba1f19a991da2d72972a8fe9a41bda}}<br />
<br />
* [https://www.postgresql.org/message-id/20210525161458.GZ3676%40telsasoft.com Document incompatibility with aggregates using system functions using anycompatiblearray]<br />
** Fixed at {{PgCommitURL|25dfb5a831a1b8a83a8a68453b4bbe38a5ef737e}}<br />
<br />
=== resolved before 14beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611340CBD300A7C4FD6B6101FB5F9@OS0PR01MB6113.jpnprd01.prod.outlook.com FailedAssertion reported in lazy_scan_heap() when running logical replication]<br />
** Fixed at: {{PgCommitURL|c9787385db47ba423d845b34d58e158551c6335d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gCXDSmFs2c%3DR%2BVGgn7FiYcLCsEFEuDNNLGfoha%3DpBE_g%40mail.gmail.com Assertion fail with window function and nested partitioned tables]<br />
** [https://www.postgresql.org/message-id/87sg8tqhsl.fsf@aurora.ydns.eu Older report]<br />
** Fixed at: {{PgCommitURL|fb2d645dd53ff571572d830e830fc8c368063802}}<br />
<br />
* [https://www.postgresql.org/message-id/1df88660-6f08-cc6e-b7e2-f85296a2bdab@oss.nttdata.com Atomic initialization of waitStart done at backend startup]<br />
** Fixed at: {{PgCommitURL|f05ed5a5cfa55878baa77a1e39d68cb09793b477}}<br />
<br />
* [https://www.postgresql.org/message-id/20210117215940.GE8560%40telsasoft.com pg_collation_actual_version() ERROR: cache lookup failed for collation 123]<br />
** Fixed at: {{PgCommitURL|0fb0a0503bfc125764c8dba4f515058145dc7f8b}}<br />
<br />
* [https://www.postgresql.org/message-id/fd3ba610085f1ff54623478cf2f7adf5af193cbb.camel@vmware.com cryptohash: missing locking functions for OpenSSL <= 1.0.2?]<br />
** Fixed at: {{PgCommitURL|2c0cefcd18161549e9e8b103f46c0f65fca84d99}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHut%2BPuPGGASnh2Dy37VYODKULVQo-5oE%3DShc6gwtRizDt%3D%3DcA%40mail.gmail.com pg_subscription - substream column?]<br />
** Fixed at: {{PgCommitURL|7efeb214ad832fa96ea950d0906b1d2b96316d15}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gcs0zGOp6JXU2mMVdthYhuQpFk%3DS3V8DOKT%3DLZC1L36Q%40mail.gmail.com TOAST compression method of index columns]<br />
** Fixed at: {{PgCommitURL|5db1fd7823a1a12e2bdad98abc8e102fd71ffbda}}<br />
<br />
* [https://www.postgresql.org/message-id/20210402235337.GA4082@ahch-to Crash with encoding conversion functions]<br />
** Fixed at: {{PgCommitURL|c4c393b3ec83ceb4b4d7f37cdd5302126377d069}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpYT10-nkSp8xXe-nbO3jmoaRyRFHbzh-RWMfAJynqgpQ@mail.gmail.com Crash with extended stats on expressions]<br />
** Fixed at: {{PgCommitURL|518442c7f334f3b05ea28b7ef50f1b551cfcc23e}}<br />
<br />
* [https://postgr.es/m/CA+TgmobwnGawnxufvqLCrcTy4HRhMepFiXQLY8YpVD+PTuwagA@mail.gmail.com Update TOAST documentation for LZ4 compression]<br />
** Fixed at: {{PgCommitURL|e8c435a824e123f43067ce6f69d66f14cfb8815e}}<br />
<br />
* [https://www.postgresql.org/message-id/20210404220802.GA728316@rfd.leadboat.com Behavior of pg_dump --extension with schemas]<br />
** Fixed at: {{PgCommitURL|344487e2db03f3cec13685a839dbc8a0e2a36750}}<br />
<br />
* [https://www.postgresql.org/message-id/OSZPR01MB631017521EE6887ADC9492E8FD759@OSZPR01MB6310.jpnprd01.prod.outlook.com psql query cancellation is broken], as are [https://www.postgresql.org/message-id/2671235.1618154047%40sss.pgh.pa.us autocommit], and [https://www.postgresql.org/message-id/YHTYOFBHDuGaz2gy@paquier.xyz error reporting]<br />
** Reverted by: {{PgCommitURL|fae65629cec824738ee11bf60f757239906d64fa}}<br />
<br />
* On Windows, collation version lookup (sometimes?) fails for names like "English_United States.1252", but works for names like "en-US".<br />
** Fixed at: {{PgCommitURL|9f12a3b95dd56c897f1aa3d756d8fb419e84a187}} -- this commit tolerates failure so at least we don't raise an error, but unfortunately we have no version information<br />
** Fixed at: {{PgCommitURL|1bf946bd43e545b86e567588b791311fe4e36a8c}} -- this commit documents the limitation<br />
<br />
* [https://www.postgresql.org/message-id/1820954.1617860500@sss.pgh.pa.us Handling of querystring inconsistent for parallel execution of SQL function bodies]<br />
** Fixed at: {{PgCommitURL|1111b2668d89bfcb6f502789158b1233ab4217a6}}<br />
<br />
* [https://www.postgresql.org/message-id/YHPkU8hFi4no4NSw@paquier.xyz Problems around compute_query_id]<br />
** Fixed at: {{PgCommitURL|db01f797dd48f826c62e1b8eea70f11fe7ff3efc}}<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com Table reference leak in logical replication]<br />
** Fixed at: {{PgCommitURL|f3b141c482552a57866c72919007d6481cd59ee3}}<br />
<br />
* [https://www.postgresql.org/message-id/20210410184226.GY6592%40telsasoft.com DETACH PARTITION CONCURRENTLY: Avoid adding redundant constraint]<br />
** Fixed at: {{PgCommitURL|7b357cc6ae}}<br />
<br />
* [https://www.postgresql.org/message-id/CC3F964B-8FA1-4A23-9D3E-6EA00BBFF0EE@enterprisedb.com Issues in PostgresNode and older major versions with multi-install]<br />
** Fixed at {{PgCommitURL|95c3a1956ec9eac686c1b69b033dd79211b72343}} and {{PgCommitURL|4c4eaf3d19201c5e2d9efebc590903dfaba0d3e5}}<br />
<br />
* [https://www.postgresql.org/message-id/3269784.1617215412%40sss.pgh.pa.us DETACH PARTITION CONCURRENTLY tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|8aba9322511f}}<br />
<br />
* [https://www.postgresql.org/message-id/551ed8c1-f531-818b-664a-2cecdab99cd8@oss.nttdata.com TRUNCATE on foreign tables and ONLY clause]<br />
** Fixed at: {{PgCommitURL|8e9ea08bae93a754d5075b7bc9c0b2bc71958bfd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zKGWEJdBbYKw7Tn7cJmYR_UjgdcXTPDqJj=dNwCETBCQ@mail.gmail.com handling of character continuation in psql broken by sql body patch]<br />
** Fixed at: {{PgCommitURL|d9a9f4b4b92ad39e3c4e6600dc61d5603ddd6e24}}<br />
<br />
* [https://www.postgresql.org/message-id/20210505210947.GA27406%40telsasoft.com cache lookup failed for statistics object 123]<br />
** Fixed at: {{PgCommitURL|8d4b311d2494ca592e30aed03b29854d864eb846}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFj8pRCL_Rjw-MCR6J7VX9OF7MR6PA5K8qUbrMvprW_e-aHkfQ%40mail.gmail.com batch fdw insert bug]<br />
** Fixed at: {{PgCommitURL|c6a01d924939306e95c8deafd09352be6a955648}}<br />
<br />
* [https://www.postgresql.org/message-id/3564817.1618420687@sss.pgh.pa.us Bogus collation version recording in recordMultipleDependencies]<br />
** Fixed at: {{PgCommitURL|ec48314708262d8ea6cdcb83f803fc83dd89e721}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/773932.1619022622@sss.pgh.pa.us Corruption issues with WAL prefetch?]<br />
** Fixed at: {{PgCommitURL|c2dc19342e05e081dc13b296787baa38352681ef}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/YIetoZGq31L84v5d@paquier.xyz Small issues with CREATE TABLE COMPRESSION]<br />
** MSVC scripts don't support builds with lz4: fixed at {{PgCommitURL|9ca40dcd4d0cad43d95a9a253fafaa9a9ba7de24}}<br />
** pg_dump includes no tests with compression methods of attributes and --no-toast-compression: fixed at {{PgCommitURL|63db0ac3f9e6bae313da67f640c95c0045b7f0ee}}<br />
** Documentation missing for --with-lz4 in installation instructions: fixed at {{PgCommitURL|02a93e7ef9612788081ef07ea1bbd0a8cc99ae99}}<br />
<br />
* [https://www.postgresql.org/message-id/20210319185247.ldebgpdaxsowiflw@alap3.anarazel.de Replication slot stats misgivings]<br />
** Fixed at: {{PgCommitURL|3fa17d37716f978f80dfcdab4e7c73f3a24e7a48}}<br />
** Fixed at: {{PgCommitURL|592f00f8dec68038301467a904ac514eddabf6cd}}<br />
** Fixed at: {{PgCommitURL|cca57c1d9bf7eeba5b81115e0b82651cf3d8e4ea}}<br />
** Fixed at: {{PgCommitURL|f5fc2f5b23d1b1dff60f8ca5dc211161df47eda4}}<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK158e9sJOfuWxfn%2B0ynrspXQU3JhNjSCbaoeSzMvnga%2Bbw%40mail.gmail.com FDW: crash with DDL and async/batch option]<br />
** Fixed at: {{PgCommitURL|a784859f4480ceaa05a00ca35311071ca33483d1}}<br />
<br />
* [https://www.postgresql.org/message-id/20210409213155.GA23912%40alvherre.pgsql should autoanalyze for partitioned tables handle ATTACH/DETACH/DROP?]<br />
** Fixed at: {{PgCommitURL|1b5617eb844cd2470a334c1d2eec66cf9b39c41a}} (docs)<br />
<br />
* [https://www.postgresql.org/message-id/CALT9ZEE7OiszofHELnjPhX%3DhV92PiKn8haSZ4_FWBAw4diaRdQ%40mail.gmail.com OOM in spgist insert]<br />
** Fixed at: {{PgCommitURL|c3c35a733c77b298d3cf7e7de2eeb4aea540a631}}<br />
<br />
== Won't Fix ==<br />
<br />
* [https://www.postgresql.org/message-id/92408.1618772924%40sss.pgh.pa.us SQL-standard function body: pg_dump should handle circular dependencies]<br />
** Owner: Peter Eisentraut<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2021 ('''Last Day to Commit Features''')<br />
* Beta 1: May 20, 2021<br />
* Beta 2: June 24, 2021<br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=36266PostgreSQL 14 Open Items2021-07-26T15:44:26Z<p>Fuzzycz: </p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/17061-dd7f4825b7da3a9d%40postgresql.org SEARCH BREADTH FIRST produces a composite column whose fields can't be accessed]<br />
** Owner: Peter Eisentraut<br />
<br />
* [https://www.postgresql.org/message-id/17066-16a37f6223a8470b@postgresql.org Cache lookup failed when null (unknown) is passed as anycompatiblemultirange]<br />
** Owner: Alexander Korotkov<br />
<br />
* [https://www.postgresql.org/message-id/TYAPR01MB5866BA57688DF2770E2F95C6F5069@TYAPR01MB5866.jpnprd01.prod.outlook.com DECLARE STATEMENT and DEALLOCATE/DESCRIBE]<br />
** Owner: Michael Meskes<br />
<br />
* [https://www.postgresql.org/message-id/b5146fb1-ad9e-7d6e-f980-98ed68744a7c%40amazon.com Logical Decoding of relation rewrite with toast does not reset toast_hash]<br />
** Owner: Amit Kapila<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/E1lS8LX-0005sr-FZ%40gemulon.postgresql.org default setting of enable_resultcache]<br />
** Owner: David Rowley<br />
<br />
* [https://www.postgresql.org/message-id/4170264.1620321747%40sss.pgh.pa.us Should we undo libpq change that leaves PQerrorMessage() nonempty after successful connect?]<br />
** Owner: Tom Lane<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201016135230.GA23633%40alvherre.pgsql CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers]<br />
** tgenabled lost on CREATE TABLE .. PARTITION OF, and on pg_dump, and comments on child triggers lost during pg_dump;<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/CAEudQAoR5e7=uMZ0otzuCVb25zTC8QQBe+2Dt1JRsa3u+XuwJg@mail.gmail.com could not rename temporary statistics file on Windows]<br />
** See {{PgCommitURL|909b449e00fc2f71e1a38569bbddbb6457d28485}} that has fixed a similar symptom for WAL segments. Most reporters of the WAL segment problem complained about this renaming issue as well.<br />
<br />
* [https://www.postgresql.org/message-id/20210422203603.fdnh3fu2mmfp2iov@alap3.anarazel.de Incorrect snapshot calculation when 2PC is in use]<br />
** Seems to be an old problem.<br />
<br />
* [https://www.postgresql.org/message-id/2591376.1621196582%40sss.pgh.pa.us snapshot-scalability logic fails after pg_upgrade, due to pg_resetwal issue]<br />
** Now seems likely that this is an old issue affecting every release, and that the snapshot-scalability work is not at fault<br />
** [https://commitfest.postgresql.org/33/3105/ Pending fix for pg_upgrade + pg_resetwal]<br />
** Owner: Bruce Momjian<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/trinity-1c565d44-159f-488b-a518-caf13883134f-1611835701633%403c-app-gmx-bap78 hashagg broken by failing to spill grouping columns]<br />
** Fixed at: {{PgCommitURL|0ff865fbe50e82f17df8a9280fa01faf270b7f3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAE-ML+_EjH_fzfq1F3RJ1=XaaNG=-Jz-i3JqkNhXiLAsM3z-Ew@mail.gmail.com PITR promote bug: Checkpointer writes to older timeline]<br />
** Fixed at: {{PgCommitURL|595b9cba2ab0cdd057e02d3c23f34a8bcfd90a2d}}<br />
<br />
* [https://www.postgresql.org/message-id/YFBcRbnBiPdGZvfW%40paquier.xyz Permission failures with WAL files in 13~ on Windows]<br />
** Fixed at: {{PgCommitURL|78c24e97dd189f62187a99ef84016d0eb35a7978}}<br />
<br />
* [https://www.postgresql.org/message-id/CANiYTQsU7yMFpQYnv=BrcRVqK_3U3mtAzAsJCaqtzsDHfsUbdQ@mail.gmail.com CLOBBER_CACHE Server crashed with segfault 11 while executing clusterdb]<br />
** Fixed at: {{PgCommitURL|9d523119fd38fd205cb9c8ea8e7cceeb54355818}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAV6ZkQRCVBh8qAY+SZiHnz+U+FqAGBBDaDTjF2yiKa2nJSLKg@mail.gmail.com Reference leak with tupledescs in plpgsql simple expressions]<br />
** Fixed at: {{PgCommitURL|c2db458c1036efae503ce5e451f8369e64c99541}}<br />
<br />
* [https://www.postgresql.org/message-id/a3be61d9-f44b-7fce-3dc8-d700fdfb6f48%402ndquadrant.com extract(julian) is undocumented and gives wrong result]<br />
** Fixed by documentation change at: {{PgCommitURL|79a5928ebcb726b7061bf265b5c6990e835e8c4f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGRY4nwxKUS_RvXFW-ugrZBYxPFFM5kjwKT5O+0+Stuga5b4+Q@mail.gmail.com lwlock dtrace probes do unnecessary work if dtrace is compiled in but disabled]<br />
** Fixed at: {{PgCommitURL|b94409a02f6122d77b5154e481c0819fed6b4c95}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/15990-eee2ac466b11293d%40postgresql.org Detoast failures after commit/rollback in plpgsql]<br />
** Fixed at: {{PgCommitURL|f21fadafaf0fb5ea4c9622d915972651273d62ce}} and {{PgCommitURL|84f5c2908dad81e8622b0406beea580e40bb03ac}}<br />
<br />
* [https://www.postgresql.org/message-id/3382681.1621381328%40sss.pgh.pa.us Subscription tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|b39630fd41f25b414d0ea9b30804f4105f2a0aff}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/534fca83789c4a378c7de379e9067d4f%40politie.nl XX000: unknown type of jsonb container.]<br />
** Fixed at: {{PgCommitURL|6ee41a301e70fc8e4ad383bad22d695f66ccb0ac}}<br />
<br />
* [https://www.postgresql.org/message-id/1884374.1617898865%40sss.pgh.pa.us Buildfarm does not test pg_stat_statements]<br />
** Fixed by buildfarm client change<br />
<br />
* [https://www.postgresql.org/message-id/17064-bb0d7904ef72add3%40postgresql.org Parallel VACUUM operations cause the error "global/pg_filenode.map contains incorrect checksum"]<br />
** Fixed at: {{PgCommitURL|b6d8d207}} and {{PgCommitURL|9b8ed0f52}}<br />
<br />
* [https://www.postgresql.org/message-id/378885e4-f85f-fc28-6c91-c4d1c080bf26%40amazon.com Assertion failure in HEAD and 13 after calling COMMIT in a stored proc]<br />
** Fixed at: {{PgCommitURL|d102aafb6259a6a412803d4b1d8c4f00aa17f67e}}<br />
<br />
* [https://www.postgresql.org/message-id/4aa370cb91ecf2f9885d98b80ad1109c%40postgrespro.ru Add PortalDrop in exec_execute_message]<br />
** Fixed at: {{PgCommitURL|bb4aed46a}} and {{PgCommitURL|4efcf47053}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20210216064214.GI28165%40telsasoft.com progress reporting for partitioned REINDEX]<br />
* [https://www.postgresql.org/message-id/YFnWBYinNf1s0Y6v@msg.df7cb.de pg_regress and tablespace removal]<br />
** [https://www.postgresql.org/message-id/YG/tf6HTZFj4hWlb@paquier.xyz Some patch]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 14beta3 ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/20210530172418.GO2082%40telsasoft.com#d6544e507234cc76b9bc0a50026cd74b \dX doesn't check pg_statistics_obj_is_visible()]<br />
** Owner: Tomas Vondra<br />
<br />
* [https://www.postgresql.org/message-id/e1b4f05d-54ec-4f51-832b-c18cf5a161c0@www.fastmail.com remove_temp_files_after_crash should be a DEVELOPER GUC]<br />
** Fixed at: {{PgCommitURL|797b0fc0b078c7b4c46ef9f2d9e47aa2d98c6c63}}<br />
<br />
* [https://www.postgresql.org/message-id/20210526001359.GE3676@telsasoft.com recovery_init_sync_method should be PGC_SIGHUP?]<br />
** Fixed at: {{PgCommitURL|34a8b64b4e5f0cd818e5cc7f98846de57938ea57}}<br />
<br />
* [https://www.postgresql.org/message-id/YNZ2mnsbDVJQrA/a@paquier.xyz OOM on palloc() when parsing service file would cause libpq to exit() without reporting a failure]<br />
** Fixed at: {{PgCommitURL|8ec00dc5cd70e0e579e9fbf8661bc46f5ccd8078}}<br />
** Additional defenses added at: {{PgCommitURL|dc227eb82ea8bf6919cd81a182a084589ddce7f3}}<br />
<br />
* [https://www.postgresql.org/message-id/17076-89a16ae835d329b9%40postgresql.org incorrect code for reporting the hash partition associated with a particular modulus]<br />
** Fixed at: {{PgCommitURL|dd2364ced98553e0217bfe8f621cd4b0970db74a}}<br />
<br />
* [https://www.postgresql.org/message-id/c5269c65-f967-77c5-ff7c-15e621c47f6a%40gmail.com Bug in multirange selectivity estimation]<br />
** Fixed at: {{PgCommitURL|322e82b77ef4acb9697c6e4259292f5671cb85bb}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/704fb6fb99ec9864a4dbeda2478337d2%40postgrespro.ru autoanalyze of partitioned table causes it to lose its relhasindex]<br />
** Fixed at: {{PgCommitURL|d700518d744e53994fdded14b23ebc15b031b0dd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAF7igB1r6wRfSCEAB-iZBKxkowWY6+dFF2jObSdd9+iVK+vHJg@mail.gmail.com Incorrect time maths in pgbench] and [https://www.postgresql.org/message-id/CAHLJuCW_8Vpcr0=t6O_gozrg3wXXWXZXDioYJd3NhvKriqgpfQ@mail.gmail.com second thread]<br />
** Fixed at: {{PgCommitURL|0e39a608ed5545cc6b9d538ac937c3c1ee8cdc36}}<br />
<br />
* [https://www.postgresql.org/message-id/60258efe-bd7e-4886-82e1-196e0cac5433%40postgresql.org unnesting multirange data types]<br />
** Fixed at: {{PgCommitURL|244ad5415557812a6ac4dc5d6e2ae908361d82c3}}<br />
<br />
=== resolved before 14beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/20210609184506.rqm5rikoikm47csf%40alap3.anarazel.de Snapshot scalability OldestXmin issue (can cause infinite loop during system catalog VACUUM)]<br />
** Fixed at: {{PgCommitURL|5a1e1d83022b976ebdec5cfa8f255c4278b75b8e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkCYR0U7zXqXo0CgFaFwUDz1WbKq8ngjzKi4+AQ5f-mYQ@mail.gmail.com Generalize INDEX_CLEANUP to allow the user to disable the optimization that has VACUUM skip indexes in marginal cases with very few LP_DEAD items/deletable TIDs.]<br />
** Fixed at: {{PgCommitURL|3499df0dee8c4ea51d264a674df5b5e31991319a}}<br />
<br />
* [https://www.postgresql.org/message-id/20210324232224.vrfiij2rxxwqqjjb@alap3.anarazel.de Questions about pg_stat_wal] also [https://www.postgresql.org/message-id/E3774ACD-7894-451E-9F13-71E097D10595@oss.nttdata.com]<br />
** Fixed at: {{PgCommitURL|d8735b8b4651f5ed50afc472e236a8e6120f07f2}}<br />
** Fixed at: {{PgCommitURL|d780d7c0882fe9a385102b292907baaceb505ed0}}<br />
<br />
* [https://www.postgresql.org/message-id/YKMO%2B2gD8R8I2O5b%40paquier.xyz pg_dumpall misses --no-toast-compression]<br />
** Fixed at: {{PgCommitURL|694da1983e9569b2a2f96cd786ead6b8dba31f1d}} <br />
<br />
* [https://www.postgresql.org/message-id/YKQnUoYV63GRJBDD%40msg.df7cb.de portability issue with pgbench's permute() function]<br />
** Fixed at: {{PgCommitURL|0f516d039d8023163e82fa51104052306068dd69}}<br />
<br />
* [https://www.postgresql.org/message-id/35457b09-36f8-add3-1d07-6034fa585ca8@oss.nttdata.com compute_query_id and pg_stat_statements]<br />
** Fixed at {{PgCommitURL|cafde58b33}} and {{PgCommitURL|354f32d01d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAOxo6X+dy-V58iEPFgst8ahPKEU+38NZzUuc+a7wDBZd4TrHMQ@mail.gmail.com Result Cache works incorrectly with unique joins]<br />
** Fixed at {{PgCommitURL|9e215378d7fbb7d4615be917917c52f246cc6c61}}<br />
<br />
* [https://www.postgresql.org/message-id/20210517204803.iyk5wwvwgtjcmc5w%40alap3.anarazel.de Move pg_attribute.attcompression to earlier in struct for reduced size?]<br />
** Fixed at {{PgCommitURL|f5024d8d7b04de2f5f4742ab433cc38160354861}}<br />
<br />
* [https://www.postgresql.org/message-id/17030-5844aecae42fe223@postgresql.org EXPLAIN can suffer from cannot decompile join alias var in plan tree]<br />
** Fixed at {{PgCommitURL|cba5c70b956810c61b3778f7041f92fbb8065acb}}<br />
<br />
* [https://www.postgresql.org/message-id/20210521211929.pcehg6f23icwstdb@alap3.anarazel.de Memory leak when rewriting tuples with recompressed toast values]<br />
** Fixed at {{PgCommitURL|fb0f5f0172edf9f63c8f70ea9c1ec043b61c770e}}<br />
<br />
* [https://www.postgresql.org/message-id/626613.1621787110%40sss.pgh.pa.us Redefine pg_attribute.attcompression]<br />
** Fixed at {{PgCommitURL|e6241d8e030fbd2746b3ea3f44e728224298f35b}}<br />
<br />
* [https://www.postgresql.org/message-id/1665197.1622065382%40sss.pgh.pa.us Undo bump of FirstBootstrapObjectId]<br />
** Fixed at {{PgCommitURL|a4390abecf0f5152cff864e82b67e5f6c8489698}}<br />
<br />
* [https://www.postgresql.org/message-id/CABOikdN-_858zojYN-2tNcHiVTw-nhxPwoQS4quExeweQfG1Ug%40mail.gmail.com Assertion failure while streaming toasted data]<br />
** Fixed at {{PgCommitURL|6f4bdf81529fdaf6744875b0be99ecb9bfb3b7e0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/7817fb9ebd6661cdf9b67dec6e129a78%40postgrespro.ru Join pushdown issue in postgres_fdw updates]<br />
** Fixed at {{PgCommitURL|f61db909dfb94f3411f8719916601a11a905b95e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoA%3D%3Df2VSw3c-Cp_y%3DWLKHMKc1D6s7g3YWsCOvgaYPpJcg%40mail.gmail.com Performance degradation of REFRESH MATERIALIZED VIEW]<br />
** Fixed at {{PgCommitURL|8e03eb92e9ad54e2f1ed8b5a73617601f6262f81}}<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK16Q4B2_KY%2BJH7rb7wQbw54AUprp7TMekGTd2T1B62yysQ%40mail.gmail.com Rescan of async Appends is broken when do_exec_prune=false]<br />
** Fixed at {{PgCommitURL|f3baaf28a6da588987b94a05a725894805c3eae9}}<br />
<br />
* [https://www.postgresql.org/message-id/504c276ab6eee000bb23d571ea9b0ced4250774e.camel%40vmware.com libpq dumps core while making an SSL connection to a server specified by hostaddr]<br />
** Fixed at {{PgCommitURL|37e1cce4ddf0be362e3093cee55493aee41bc423}}<br />
<br />
* [https://www.postgresql.org/message-id/B4A3AF82-79ED-4F4C-A4E5-CD2622098972%40enterprisedb.com logical replication of truncate command with trigger causes Assert]<br />
** Fixed at {{PgCommitURL|3a09d75b4f6cabc8331e228b6988dbfcd9afdfbe}}<br />
<br />
* [https://www.postgresql.org/message-id/3742981.1621533210%40sss.pgh.pa.us Reconsider catalog representation and uniqueness rules for procedures with output-only arguments]<br />
** Fixed at {{PgCommitURL|e56bce5d43789cce95d099554ae9593ada92b3b7}}<br />
<br />
* [https://www.postgresql.org/message-id/20210527003144.xxqppojoiwurc2iz@alap3.anarazel.de Performance regression of VACUUM FULL with the addition of recompression path in tuple rewrite]<br />
** Fixed at {{PgCommitURL|dbab0c07e5ba1f19a991da2d72972a8fe9a41bda}}<br />
<br />
* [https://www.postgresql.org/message-id/20210525161458.GZ3676%40telsasoft.com Document incompatibility with aggregates using system functions using anycompatiblearray]<br />
** Fixed at {{PgCommitURL|25dfb5a831a1b8a83a8a68453b4bbe38a5ef737e}}<br />
<br />
=== resolved before 14beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611340CBD300A7C4FD6B6101FB5F9@OS0PR01MB6113.jpnprd01.prod.outlook.com FailedAssertion reported in lazy_scan_heap() when running logical replication]<br />
** Fixed at: {{PgCommitURL|c9787385db47ba423d845b34d58e158551c6335d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gCXDSmFs2c%3DR%2BVGgn7FiYcLCsEFEuDNNLGfoha%3DpBE_g%40mail.gmail.com Assertion fail with window function and nested partitioned tables]<br />
** [https://www.postgresql.org/message-id/87sg8tqhsl.fsf@aurora.ydns.eu Older report]<br />
** Fixed at: {{PgCommitURL|fb2d645dd53ff571572d830e830fc8c368063802}}<br />
<br />
* [https://www.postgresql.org/message-id/1df88660-6f08-cc6e-b7e2-f85296a2bdab@oss.nttdata.com Atomic initialization of waitStart done at backend startup]<br />
** Fixed at: {{PgCommitURL|f05ed5a5cfa55878baa77a1e39d68cb09793b477}}<br />
<br />
* [https://www.postgresql.org/message-id/20210117215940.GE8560%40telsasoft.com pg_collation_actual_version() ERROR: cache lookup failed for collation 123]<br />
** Fixed at: {{PgCommitURL|0fb0a0503bfc125764c8dba4f515058145dc7f8b}}<br />
<br />
* [https://www.postgresql.org/message-id/fd3ba610085f1ff54623478cf2f7adf5af193cbb.camel@vmware.com cryptohash: missing locking functions for OpenSSL <= 1.0.2?]<br />
** Fixed at: {{PgCommitURL|2c0cefcd18161549e9e8b103f46c0f65fca84d99}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHut%2BPuPGGASnh2Dy37VYODKULVQo-5oE%3DShc6gwtRizDt%3D%3DcA%40mail.gmail.com pg_subscription - substream column?]<br />
** Fixed at: {{PgCommitURL|7efeb214ad832fa96ea950d0906b1d2b96316d15}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gcs0zGOp6JXU2mMVdthYhuQpFk%3DS3V8DOKT%3DLZC1L36Q%40mail.gmail.com TOAST compression method of index columns]<br />
** Fixed at: {{PgCommitURL|5db1fd7823a1a12e2bdad98abc8e102fd71ffbda}}<br />
<br />
* [https://www.postgresql.org/message-id/20210402235337.GA4082@ahch-to Crash with encoding conversion functions]<br />
** Fixed at: {{PgCommitURL|c4c393b3ec83ceb4b4d7f37cdd5302126377d069}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpYT10-nkSp8xXe-nbO3jmoaRyRFHbzh-RWMfAJynqgpQ@mail.gmail.com Crash with extended stats on expressions]<br />
** Fixed at: {{PgCommitURL|518442c7f334f3b05ea28b7ef50f1b551cfcc23e}}<br />
<br />
* [https://postgr.es/m/CA+TgmobwnGawnxufvqLCrcTy4HRhMepFiXQLY8YpVD+PTuwagA@mail.gmail.com Update TOAST documentation for LZ4 compression]<br />
** Fixed at: {{PgCommitURL|e8c435a824e123f43067ce6f69d66f14cfb8815e}}<br />
<br />
* [https://www.postgresql.org/message-id/20210404220802.GA728316@rfd.leadboat.com Behavior of pg_dump --extension with schemas]<br />
** Fixed at: {{PgCommitURL|344487e2db03f3cec13685a839dbc8a0e2a36750}}<br />
<br />
* [https://www.postgresql.org/message-id/OSZPR01MB631017521EE6887ADC9492E8FD759@OSZPR01MB6310.jpnprd01.prod.outlook.com psql query cancellation is broken], as are [https://www.postgresql.org/message-id/2671235.1618154047%40sss.pgh.pa.us autocommit], and [https://www.postgresql.org/message-id/YHTYOFBHDuGaz2gy@paquier.xyz error reporting]<br />
** Reverted by: {{PgCommitURL|fae65629cec824738ee11bf60f757239906d64fa}}<br />
<br />
* On Windows, collation version lookup (sometimes?) fails for names like "English_United States.1252", but works for names like "en-US".<br />
** Fixed at: {{PgCommitURL|9f12a3b95dd56c897f1aa3d756d8fb419e84a187}} -- this commit tolerates failure so at least we don't raise an error, but unfortunately we have no version information<br />
** Fixed at: {{PgCommitURL|1bf946bd43e545b86e567588b791311fe4e36a8c}} -- this commit documents the limitation<br />
<br />
* [https://www.postgresql.org/message-id/1820954.1617860500@sss.pgh.pa.us Handling of querystring inconsistent for parallel execution of SQL function bodies]<br />
** Fixed at: {{PgCommitURL|1111b2668d89bfcb6f502789158b1233ab4217a6}}<br />
<br />
* [https://www.postgresql.org/message-id/YHPkU8hFi4no4NSw@paquier.xyz Problems around compute_query_id]<br />
** Fixed at: {{PgCommitURL|db01f797dd48f826c62e1b8eea70f11fe7ff3efc}}<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com Table reference leak in logical replication]<br />
** Fixed at: {{PgCommitURL|f3b141c482552a57866c72919007d6481cd59ee3}}<br />
<br />
* [https://www.postgresql.org/message-id/20210410184226.GY6592%40telsasoft.com DETACH PARTITION CONCURRENTLY: Avoid adding redundant constraint]<br />
** Fixed at: {{PgCommitURL|7b357cc6ae}}<br />
<br />
* [https://www.postgresql.org/message-id/CC3F964B-8FA1-4A23-9D3E-6EA00BBFF0EE@enterprisedb.com Issues in PostgresNode and older major versions with multi-install]<br />
** Fixed at {{PgCommitURL|95c3a1956ec9eac686c1b69b033dd79211b72343}} and {{PgCommitURL|4c4eaf3d19201c5e2d9efebc590903dfaba0d3e5}}<br />
<br />
* [https://www.postgresql.org/message-id/3269784.1617215412%40sss.pgh.pa.us DETACH PARTITION CONCURRENTLY tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|8aba9322511f}}<br />
<br />
* [https://www.postgresql.org/message-id/551ed8c1-f531-818b-664a-2cecdab99cd8@oss.nttdata.com TRUNCATE on foreign tables and ONLY clause]<br />
** Fixed at: {{PgCommitURL|8e9ea08bae93a754d5075b7bc9c0b2bc71958bfd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zKGWEJdBbYKw7Tn7cJmYR_UjgdcXTPDqJj=dNwCETBCQ@mail.gmail.com handling of character continuation in psql broken by sql body patch]<br />
** Fixed at: {{PgCommitURL|d9a9f4b4b92ad39e3c4e6600dc61d5603ddd6e24}}<br />
<br />
* [https://www.postgresql.org/message-id/20210505210947.GA27406%40telsasoft.com cache lookup failed for statistics object 123]<br />
** Fixed at: {{PgCommitURL|8d4b311d2494ca592e30aed03b29854d864eb846}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFj8pRCL_Rjw-MCR6J7VX9OF7MR6PA5K8qUbrMvprW_e-aHkfQ%40mail.gmail.com batch fdw insert bug]<br />
** Fixed at: {{PgCommitURL|c6a01d924939306e95c8deafd09352be6a955648}}<br />
<br />
* [https://www.postgresql.org/message-id/3564817.1618420687@sss.pgh.pa.us Bogus collation version recording in recordMultipleDependencies]<br />
** Fixed at: {{PgCommitURL|ec48314708262d8ea6cdcb83f803fc83dd89e721}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/773932.1619022622@sss.pgh.pa.us Corruption issues with WAL prefetch?]<br />
** Fixed at: {{PgCommitURL|c2dc19342e05e081dc13b296787baa38352681ef}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/YIetoZGq31L84v5d@paquier.xyz Small issues with CREATE TABLE COMPRESSION]<br />
** MSVC scripts don't support builds with lz4: fixed at {{PgCommitURL|9ca40dcd4d0cad43d95a9a253fafaa9a9ba7de24}}<br />
** pg_dump includes no tests with compression methods of attributes and --no-toast-compression: fixed at {{PgCommitURL|63db0ac3f9e6bae313da67f640c95c0045b7f0ee}}<br />
** Documentation missing for --with-lz4 in installation instructions: fixed at {{PgCommitURL|02a93e7ef9612788081ef07ea1bbd0a8cc99ae99}}<br />
<br />
* [https://www.postgresql.org/message-id/20210319185247.ldebgpdaxsowiflw@alap3.anarazel.de Replication slot stats misgivings]<br />
** Fixed at: {{PgCommitURL|3fa17d37716f978f80dfcdab4e7c73f3a24e7a48}}<br />
** Fixed at: {{PgCommitURL|592f00f8dec68038301467a904ac514eddabf6cd}}<br />
** Fixed at: {{PgCommitURL|cca57c1d9bf7eeba5b81115e0b82651cf3d8e4ea}}<br />
** Fixed at: {{PgCommitURL|f5fc2f5b23d1b1dff60f8ca5dc211161df47eda4}}<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK158e9sJOfuWxfn%2B0ynrspXQU3JhNjSCbaoeSzMvnga%2Bbw%40mail.gmail.com FDW: crash with DDL and async/batch option]<br />
** Fixed at: {{PgCommitURL|a784859f4480ceaa05a00ca35311071ca33483d1}}<br />
<br />
* [https://www.postgresql.org/message-id/20210409213155.GA23912%40alvherre.pgsql should autoanalyze for partitioned tables handle ATTACH/DETACH/DROP?]<br />
** Fixed at: {{PgCommitURL|1b5617eb844cd2470a334c1d2eec66cf9b39c41a}} (docs)<br />
<br />
* [https://www.postgresql.org/message-id/CALT9ZEE7OiszofHELnjPhX%3DhV92PiKn8haSZ4_FWBAw4diaRdQ%40mail.gmail.com OOM in spgist insert]<br />
** Fixed at: {{PgCommitURL|c3c35a733c77b298d3cf7e7de2eeb4aea540a631}}<br />
<br />
== Won't Fix ==<br />
<br />
* [https://www.postgresql.org/message-id/92408.1618772924%40sss.pgh.pa.us SQL-standard function body: pg_dump should handle circular dependencies]<br />
** Owner: Peter Eisentraut<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2021 ('''Last Day to Commit Features''')<br />
* Beta 1: May 20, 2021<br />
* Beta 2: June 24, 2021<br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_14_Open_Items&diff=36146PostgreSQL 14 Open Items2021-06-06T11:15:21Z<p>Fuzzycz: </p>
<hr />
<div>== Open Issues ==<br />
<br />
'''NOTE''': Please place new open items at the end of the list.<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkCYR0U7zXqXo0CgFaFwUDz1WbKq8ngjzKi4+AQ5f-mYQ@mail.gmail.com Generalize INDEX_CLEANUP to allow the user to disable the optimization that has VACUUM skip indexes in marginal cases with very few LP_DEAD items/deletable TIDs.]<br />
** Owner: Peter Geoghegan<br />
<br />
* [https://www.postgresql.org/message-id/2591376.1621196582%40sss.pgh.pa.us snapshot-scalability logic fails after pg_resetwal]<br />
** Owner: Andres Freund<br />
<br />
* [https://www.postgresql.org/message-id/3742981.1621533210%40sss.pgh.pa.us Reconsider catalog representation and uniqueness rules for procedures with output-only arguments]<br />
** Owner: Peter Eisentraut<br />
<br />
* [https://www.postgresql.org/message-id/20210525161458.GZ3676%40telsasoft.com Document incompatibility with aggregates using system functions using anycompatiblearray]<br />
** Owner: Bruce Momjian<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK16Q4B2_KY%2BJH7rb7wQbw54AUprp7TMekGTd2T1B62yysQ%40mail.gmail.com Rescan of async Appends is broken when do_exec_prune=false]<br />
** Owner: Etsuro Fujita<br />
<br />
* [https://www.postgresql.org/message-id/20210526001359.GE3676@telsasoft.com recovery_init_sync_method should be PGC_SIGHUP?]<br />
** Owner: Thomas Munro<br />
<br />
* [https://www.postgresql.org/message-id/20210527003144.xxqppojoiwurc2iz@alap3.anarazel.de Performance regression of VACUUM FULL with the addition of recompression path in tuple rewrite]<br />
** Owner: Robert Haas<br />
<br />
* [https://www.postgresql.org/message-id/504c276ab6eee000bb23d571ea9b0ced4250774e.camel%40vmware.com libpq dumps core while making an SSL connection to a server specified by hostaddr]<br />
** Owner: Peter Eisentraut<br />
<br />
== Decisions to Recheck Mid-Beta ==<br />
<br />
* [https://www.postgresql.org/message-id/E1lS8LX-0005sr-FZ%40gemulon.postgresql.org default setting of enable_resultcache]<br />
** Owner: David Rowley<br />
<br />
* [https://www.postgresql.org/message-id/4170264.1620321747%40sss.pgh.pa.us Should we undo libpq change that leaves PQerrorMessage() nonempty after successful connect?]<br />
** Owner: Tom Lane<br />
** [https://www.postgresql.org/message-id/YLRZH6CWs9N6Pusy@paquier.xyz Seems to have some impact on ECPG tests]<br />
<br />
== Older bugs affecting stable branches ==<br />
<br />
=== Live issues ===<br />
<br />
* [https://www.postgresql.org/message-id/CAH2-WzkjjCoq5Y4LeeHJcjYJVxGm3M3SAWZ0%3D6J8K1FPSC9K0w%40mail.gmail.com REINDEX on a system catalog can leave index with two index tuples whose heap TIDs match]<br />
** In other words, there is a rare case where the HOT invariant is violated. Same HOT chain is indexed twice due to confusion about which precise heap tuple should be indexed.<br />
** Unclear what the user impact is.<br />
** Affects all stable branches.<br />
<br />
* [https://www.postgresql.org/message-id/20201016135230.GA23633%40alvherre.pgsql CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers]<br />
** tgenabled lost on CREATE TABLE .. PARTITION OF, and on pg_dump, and comments on child triggers lost during pg_dump;<br />
<br />
* [https://www.postgresql.org/message-id/20201001021609.GC8476%40telsasoft.com memory leak with JIT inlining]<br />
** [https://www.postgresql.org/message-id/flat/20210331040751.GU4431%40telsasoft.com#cc34872765add8e483e05009212d9d39 Another report of (same?) issue and reproducer]<br />
** [https://www.postgresql.org/message-id/flat/9f73e655-14b8-feaf-bd66-c0f506224b9e%40stephans-server.de Another report]<br />
** [https://www.postgresql.org/message-id/flat/16707-f5df308978a55bf8%40postgresql.org Another report]<br />
<br />
* [https://www.postgresql.org/message-id/1884374.1617898865%40sss.pgh.pa.us Buildfarm does not test pg_stat_statements]<br />
<br />
* [https://www.postgresql.org/message-id/CAEudQAoR5e7=uMZ0otzuCVb25zTC8QQBe+2Dt1JRsa3u+XuwJg@mail.gmail.com could not rename temporary statistics file on Windows]<br />
** See {{PgCommitURL|909b449e00fc2f71e1a38569bbddbb6457d28485}} that has fixed a similar symptom for WAL segments. Most reporters of the WAL segment problem complained about this renaming issue as well.<br />
<br />
* [https://www.postgresql.org/message-id/20210422203603.fdnh3fu2mmfp2iov@alap3.anarazel.de Incorrect snapshot calculation when 2PC is in use]<br />
** Seems to be an old problem.<br />
<br />
* [https://www.postgresql.org/message-id/4aa370cb91ecf2f9885d98b80ad1109c%40postgrespro.ru Add PortalDrop in exec_execute_message]<br />
<br />
=== Fixed issues ===<br />
<br />
* [https://www.postgresql.org/message-id/flat/trinity-1c565d44-159f-488b-a518-caf13883134f-1611835701633%403c-app-gmx-bap78 hashagg broken by failing to spill grouping columns]<br />
** Fixed at: {{PgCommitURL|0ff865fbe50e82f17df8a9280fa01faf270b7f3f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAE-ML+_EjH_fzfq1F3RJ1=XaaNG=-Jz-i3JqkNhXiLAsM3z-Ew@mail.gmail.com PITR promote bug: Checkpointer writes to older timeline]<br />
** Fixed at: {{PgCommitURL|595b9cba2ab0cdd057e02d3c23f34a8bcfd90a2d}}<br />
<br />
* [https://www.postgresql.org/message-id/YFBcRbnBiPdGZvfW%40paquier.xyz Permission failures with WAL files in 13~ on Windows]<br />
** Fixed at: {{PgCommitURL|78c24e97dd189f62187a99ef84016d0eb35a7978}}<br />
<br />
* [https://www.postgresql.org/message-id/CANiYTQsU7yMFpQYnv=BrcRVqK_3U3mtAzAsJCaqtzsDHfsUbdQ@mail.gmail.com CLOBBER_CACHE Server crashed with segfault 11 while executing clusterdb]<br />
** Fixed at: {{PgCommitURL|9d523119fd38fd205cb9c8ea8e7cceeb54355818}}<br />
<br />
* [https://www.postgresql.org/message-id/CAAV6ZkQRCVBh8qAY+SZiHnz+U+FqAGBBDaDTjF2yiKa2nJSLKg@mail.gmail.com Reference leak with tupledescs in plpgsql simple expressions]<br />
** Fixed at: {{PgCommitURL|c2db458c1036efae503ce5e451f8369e64c99541}}<br />
<br />
* [https://www.postgresql.org/message-id/a3be61d9-f44b-7fce-3dc8-d700fdfb6f48%402ndquadrant.com extract(julian) is undocumented and gives wrong result]<br />
** Fixed by documentation change at: {{PgCommitURL|79a5928ebcb726b7061bf265b5c6990e835e8c4f}}<br />
<br />
* [https://www.postgresql.org/message-id/CAGRY4nwxKUS_RvXFW-ugrZBYxPFFM5kjwKT5O+0+Stuga5b4+Q@mail.gmail.com lwlock dtrace probes do unnecessary work if dtrace is compiled in but disabled]<br />
** Fixed at: {{PgCommitURL|b94409a02f6122d77b5154e481c0819fed6b4c95}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/15990-eee2ac466b11293d%40postgresql.org Detoast failures after commit/rollback in plpgsql]<br />
** Fixed at: {{PgCommitURL|f21fadafaf0fb5ea4c9622d915972651273d62ce}} and {{PgCommitURL|84f5c2908dad81e8622b0406beea580e40bb03ac}}<br />
<br />
* [https://www.postgresql.org/message-id/3382681.1621381328%40sss.pgh.pa.us Subscription tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|b39630fd41f25b414d0ea9b30804f4105f2a0aff}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/534fca83789c4a378c7de379e9067d4f%40politie.nl XX000: unknown type of jsonb container.]<br />
** Fixed at: {{PgCommitURL|6ee41a301e70fc8e4ad383bad22d695f66ccb0ac}}<br />
<br />
=== Nothing to do ===<br />
<br />
== Non-bugs ==<br />
<br />
* [https://www.postgresql.org/message-id/20210216064214.GI28165%40telsasoft.com progress reporting for partitioned REINDEX]<br />
* [https://www.postgresql.org/message-id/YFnWBYinNf1s0Y6v@msg.df7cb.de pg_regress and tablespace removal]<br />
** [https://www.postgresql.org/message-id/YG/tf6HTZFj4hWlb@paquier.xyz Some patch]<br />
<br />
== Resolved Issues ==<br />
<br />
=== resolved before 14beta2 ===<br />
<br />
* [https://www.postgresql.org/message-id/20210324232224.vrfiij2rxxwqqjjb@alap3.anarazel.de Questions about pg_stat_wal] also [https://www.postgresql.org/message-id/E3774ACD-7894-451E-9F13-71E097D10595@oss.nttdata.com]<br />
** Fixed at: {{PgCommitURL|d8735b8b4651f5ed50afc472e236a8e6120f07f2}}<br />
** Fixed at: {{PgCommitURL|d780d7c0882fe9a385102b292907baaceb505ed0}}<br />
<br />
* [https://www.postgresql.org/message-id/YKMO%2B2gD8R8I2O5b%40paquier.xyz pg_dumpall misses --no-toast-compression]<br />
** Fixed at: {{PgCommitURL|694da1983e9569b2a2f96cd786ead6b8dba31f1d}} <br />
<br />
* [https://www.postgresql.org/message-id/YKQnUoYV63GRJBDD%40msg.df7cb.de portability issue with pgbench's permute() function]<br />
** Fixed at: {{PgCommitURL|0f516d039d8023163e82fa51104052306068dd69}}<br />
<br />
* [https://www.postgresql.org/message-id/35457b09-36f8-add3-1d07-6034fa585ca8@oss.nttdata.com compute_query_id and pg_stat_statements]<br />
** Fixed at {{PgCommitURL|cafde58b33}} and {{PgCommitURL|354f32d01d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAOxo6X+dy-V58iEPFgst8ahPKEU+38NZzUuc+a7wDBZd4TrHMQ@mail.gmail.com Result Cache works incorrectly with unique joins]<br />
** Fixed at {{PgCommitURL|9e215378d7fbb7d4615be917917c52f246cc6c61}}<br />
<br />
* [https://www.postgresql.org/message-id/20210517204803.iyk5wwvwgtjcmc5w%40alap3.anarazel.de Move pg_attribute.attcompression to earlier in struct for reduced size?]<br />
** Fixed at {{PgCommitURL|f5024d8d7b04de2f5f4742ab433cc38160354861}}<br />
<br />
* [https://www.postgresql.org/message-id/17030-5844aecae42fe223@postgresql.org EXPLAIN can suffer from cannot decompile join alias var in plan tree]<br />
** Fixed at {{PgCommitURL|cba5c70b956810c61b3778f7041f92fbb8065acb}}<br />
<br />
* [https://www.postgresql.org/message-id/20210521211929.pcehg6f23icwstdb@alap3.anarazel.de Memory leak when rewriting tuples with recompressed toast values]<br />
** Fixed at {{PgCommitURL|fb0f5f0172edf9f63c8f70ea9c1ec043b61c770e}}<br />
<br />
* [https://www.postgresql.org/message-id/626613.1621787110%40sss.pgh.pa.us Redefine pg_attribute.attcompression]<br />
** Fixed at {{PgCommitURL|e6241d8e030fbd2746b3ea3f44e728224298f35b}}<br />
<br />
* [https://www.postgresql.org/message-id/1665197.1622065382%40sss.pgh.pa.us Undo bump of FirstBootstrapObjectId]<br />
** Fixed at {{PgCommitURL|a4390abecf0f5152cff864e82b67e5f6c8489698}}<br />
<br />
* [https://www.postgresql.org/message-id/CABOikdN-_858zojYN-2tNcHiVTw-nhxPwoQS4quExeweQfG1Ug%40mail.gmail.com Assertion failure while streaming toasted data]<br />
** Fixed at {{PgCommitURL|6f4bdf81529fdaf6744875b0be99ecb9bfb3b7e0}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/7817fb9ebd6661cdf9b67dec6e129a78%40postgrespro.ru Join pushdown issue in postgres_fdw updates]<br />
** Fixed at {{PgCommitURL|f61db909dfb94f3411f8719916601a11a905b95e}}<br />
<br />
* [https://www.postgresql.org/message-id/CAD21AoA%3D%3Df2VSw3c-Cp_y%3DWLKHMKc1D6s7g3YWsCOvgaYPpJcg%40mail.gmail.com Performance degradation of REFRESH MATERIALIZED VIEW]<br />
** Fixed at {{PgCommitURL|8e03eb92e9ad54e2f1ed8b5a73617601f6262f81}}<br />
<br />
=== resolved before 14beta1 ===<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611340CBD300A7C4FD6B6101FB5F9@OS0PR01MB6113.jpnprd01.prod.outlook.com FailedAssertion reported in lazy_scan_heap() when running logical replication]<br />
** Fixed at: {{PgCommitURL|c9787385db47ba423d845b34d58e158551c6335d}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gCXDSmFs2c%3DR%2BVGgn7FiYcLCsEFEuDNNLGfoha%3DpBE_g%40mail.gmail.com Assertion fail with window function and nested partitioned tables]<br />
** [https://www.postgresql.org/message-id/87sg8tqhsl.fsf@aurora.ydns.eu Older report]<br />
** Fixed at: {{PgCommitURL|fb2d645dd53ff571572d830e830fc8c368063802}}<br />
<br />
* [https://www.postgresql.org/message-id/1df88660-6f08-cc6e-b7e2-f85296a2bdab@oss.nttdata.com Atomic initialization of waitStart done at backend startup]<br />
** Fixed at: {{PgCommitURL|f05ed5a5cfa55878baa77a1e39d68cb09793b477}}<br />
<br />
* [https://www.postgresql.org/message-id/20210117215940.GE8560%40telsasoft.com pg_collation_actual_version() ERROR: cache lookup failed for collation 123]<br />
** Fixed at: {{PgCommitURL|0fb0a0503bfc125764c8dba4f515058145dc7f8b}}<br />
<br />
* [https://www.postgresql.org/message-id/fd3ba610085f1ff54623478cf2f7adf5af193cbb.camel@vmware.com cryptohash: missing locking functions for OpenSSL <= 1.0.2?]<br />
** Fixed at: {{PgCommitURL|2c0cefcd18161549e9e8b103f46c0f65fca84d99}}<br />
<br />
* [https://www.postgresql.org/message-id/CAHut%2BPuPGGASnh2Dy37VYODKULVQo-5oE%3DShc6gwtRizDt%3D%3DcA%40mail.gmail.com pg_subscription - substream column?]<br />
** Fixed at: {{PgCommitURL|7efeb214ad832fa96ea950d0906b1d2b96316d15}}<br />
<br />
* [https://www.postgresql.org/message-id/CAJKUy5gcs0zGOp6JXU2mMVdthYhuQpFk%3DS3V8DOKT%3DLZC1L36Q%40mail.gmail.com TOAST compression method of index columns]<br />
** Fixed at: {{PgCommitURL|5db1fd7823a1a12e2bdad98abc8e102fd71ffbda}}<br />
<br />
* [https://www.postgresql.org/message-id/20210402235337.GA4082@ahch-to Crash with encoding conversion functions]<br />
** Fixed at: {{PgCommitURL|c4c393b3ec83ceb4b4d7f37cdd5302126377d069}}<br />
<br />
* [https://www.postgresql.org/message-id/CAApHDvpYT10-nkSp8xXe-nbO3jmoaRyRFHbzh-RWMfAJynqgpQ@mail.gmail.com Crash with extended stats on expressions]<br />
** Fixed at: {{PgCommitURL|518442c7f334f3b05ea28b7ef50f1b551cfcc23e}}<br />
<br />
* [https://postgr.es/m/CA+TgmobwnGawnxufvqLCrcTy4HRhMepFiXQLY8YpVD+PTuwagA@mail.gmail.com Update TOAST documentation for LZ4 compression]<br />
** Fixed at: {{PgCommitURL|e8c435a824e123f43067ce6f69d66f14cfb8815e}}<br />
<br />
* [https://www.postgresql.org/message-id/20210404220802.GA728316@rfd.leadboat.com Behavior of pg_dump --extension with schemas]<br />
** Fixed at: {{PgCommitURL|344487e2db03f3cec13685a839dbc8a0e2a36750}}<br />
<br />
* [https://www.postgresql.org/message-id/OSZPR01MB631017521EE6887ADC9492E8FD759@OSZPR01MB6310.jpnprd01.prod.outlook.com psql query cancellation is broken], as are [https://www.postgresql.org/message-id/2671235.1618154047%40sss.pgh.pa.us autocommit], and [https://www.postgresql.org/message-id/YHTYOFBHDuGaz2gy@paquier.xyz error reporting]<br />
** Reverted by: {{PgCommitURL|fae65629cec824738ee11bf60f757239906d64fa}}<br />
<br />
* On Windows, collation version lookup (sometimes?) fails for names like "English_United States.1252", but works for names like "en-US".<br />
** Fixed at: {{PgCommitURL|9f12a3b95dd56c897f1aa3d756d8fb419e84a187}} -- this commit tolerates failure so at least we don't raise an error, but unfortunately we have no version information<br />
** Fixed at: {{PgCommitURL|1bf946bd43e545b86e567588b791311fe4e36a8c}} -- this commit documents the limitation<br />
<br />
* [https://www.postgresql.org/message-id/1820954.1617860500@sss.pgh.pa.us Handling of querystring inconsistent for parallel execution of SQL function bodies]<br />
** Fixed at: {{PgCommitURL|1111b2668d89bfcb6f502789158b1233ab4217a6}}<br />
<br />
* [https://www.postgresql.org/message-id/YHPkU8hFi4no4NSw@paquier.xyz Problems around compute_query_id]<br />
** Fixed at: {{PgCommitURL|db01f797dd48f826c62e1b8eea70f11fe7ff3efc}}<br />
<br />
* [https://www.postgresql.org/message-id/OS0PR01MB611383FA0FE92EB9DE21946AFB769@OS0PR01MB6113.jpnprd01.prod.outlook.com Table reference leak in logical replication]<br />
** Fixed at: {{PgCommitURL|f3b141c482552a57866c72919007d6481cd59ee3}}<br />
<br />
* [https://www.postgresql.org/message-id/20210410184226.GY6592%40telsasoft.com DETACH PARTITION CONCURRENTLY: Avoid adding redundant constraint]<br />
** Fixed at: {{PgCommitURL|7b357cc6ae}}<br />
<br />
* [https://www.postgresql.org/message-id/CC3F964B-8FA1-4A23-9D3E-6EA00BBFF0EE@enterprisedb.com Issues in PostgresNode and older major versions with multi-install]<br />
** Fixed at {{PgCommitURL|95c3a1956ec9eac686c1b69b033dd79211b72343}} and {{PgCommitURL|4c4eaf3d19201c5e2d9efebc590903dfaba0d3e5}}<br />
<br />
* [https://www.postgresql.org/message-id/3269784.1617215412%40sss.pgh.pa.us DETACH PARTITION CONCURRENTLY tests fail under CLOBBER_CACHE_ALWAYS]<br />
** Fixed at: {{PgCommitURL|8aba9322511f}}<br />
<br />
* [https://www.postgresql.org/message-id/551ed8c1-f531-818b-664a-2cecdab99cd8@oss.nttdata.com TRUNCATE on foreign tables and ONLY clause]<br />
** Fixed at: {{PgCommitURL|8e9ea08bae93a754d5075b7bc9c0b2bc71958bfd}}<br />
<br />
* [https://www.postgresql.org/message-id/CAMkU=1zKGWEJdBbYKw7Tn7cJmYR_UjgdcXTPDqJj=dNwCETBCQ@mail.gmail.com handling of character continuation in psql broken by sql body patch]<br />
** Fixed at: {{PgCommitURL|d9a9f4b4b92ad39e3c4e6600dc61d5603ddd6e24}}<br />
<br />
* [https://www.postgresql.org/message-id/20210505210947.GA27406%40telsasoft.com cache lookup failed for statistics object 123]<br />
** Fixed at: {{PgCommitURL|8d4b311d2494ca592e30aed03b29854d864eb846}}<br />
<br />
* [https://www.postgresql.org/message-id/flat/CAFj8pRCL_Rjw-MCR6J7VX9OF7MR6PA5K8qUbrMvprW_e-aHkfQ%40mail.gmail.com batch fdw insert bug]<br />
** Fixed at: {{PgCommitURL|c6a01d924939306e95c8deafd09352be6a955648}}<br />
<br />
* [https://www.postgresql.org/message-id/3564817.1618420687@sss.pgh.pa.us Bogus collation version recording in recordMultipleDependencies]<br />
** Fixed at: {{PgCommitURL|ec48314708262d8ea6cdcb83f803fc83dd89e721}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/773932.1619022622@sss.pgh.pa.us Corruption issues with WAL prefetch?]<br />
** Fixed at: {{PgCommitURL|c2dc19342e05e081dc13b296787baa38352681ef}} (Feature revert)<br />
<br />
* [https://www.postgresql.org/message-id/YIetoZGq31L84v5d@paquier.xyz Small issues with CREATE TABLE COMPRESSION]<br />
** MSVC scripts don't support builds with lz4: fixed at {{PgCommitURL|9ca40dcd4d0cad43d95a9a253fafaa9a9ba7de24}}<br />
** pg_dump includes no tests with compression methods of attributes and --no-toast-compression: fixed at {{PgCommitURL|63db0ac3f9e6bae313da67f640c95c0045b7f0ee}}<br />
** Documentation missing for --with-lz4 in installation instructions: fixed at {{PgCommitURL|02a93e7ef9612788081ef07ea1bbd0a8cc99ae99}}<br />
<br />
* [https://www.postgresql.org/message-id/20210319185247.ldebgpdaxsowiflw@alap3.anarazel.de Replication slot stats misgivings]<br />
** Fixed at: {{PgCommitURL|3fa17d37716f978f80dfcdab4e7c73f3a24e7a48}}<br />
** Fixed at: {{PgCommitURL|592f00f8dec68038301467a904ac514eddabf6cd}}<br />
** Fixed at: {{PgCommitURL|cca57c1d9bf7eeba5b81115e0b82651cf3d8e4ea}}<br />
** Fixed at: {{PgCommitURL|f5fc2f5b23d1b1dff60f8ca5dc211161df47eda4}}<br />
<br />
* [https://www.postgresql.org/message-id/CAPmGK158e9sJOfuWxfn%2B0ynrspXQU3JhNjSCbaoeSzMvnga%2Bbw%40mail.gmail.com FDW: crash with DDL and async/batch option]<br />
** Fixed at: {{PgCommitURL|a784859f4480ceaa05a00ca35311071ca33483d1}}<br />
<br />
* [https://www.postgresql.org/message-id/20210409213155.GA23912%40alvherre.pgsql should autoanalyze for partitioned tables handle ATTACH/DETACH/DROP?]<br />
** Fixed at: {{PgCommitURL|1b5617eb844cd2470a334c1d2eec66cf9b39c41a}} (docs)<br />
<br />
* [https://www.postgresql.org/message-id/CALT9ZEE7OiszofHELnjPhX%3DhV92PiKn8haSZ4_FWBAw4diaRdQ%40mail.gmail.com OOM in spgist insert]<br />
** Fixed at: {{PgCommitURL|c3c35a733c77b298d3cf7e7de2eeb4aea540a631}}<br />
<br />
== Won't Fix ==<br />
<br />
* [https://www.postgresql.org/message-id/92408.1618772924%40sss.pgh.pa.us SQL-standard function body: pg_dump should handle circular dependencies]<br />
** Owner: Peter Eisentraut<br />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
<br />
* Feature Freeze: April 7, 2021 ('''Last Day to Commit Features''')<br />
* Beta 1: May 20, 2021<br />
* Beta 2: <br />
* Beta 3: <br />
* RC 1: <br />
* GA: <br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Speaker_Bureau&diff=35460Speaker Bureau2020-10-14T09:19:14Z<p>Fuzzycz: </p>
<hr />
<div>In order to help with the challenge of finding speakers for meetups please add your name to this page if you are willing to speak at a meetup. Currently (2020) the meetups will be virtual. At a minimum add your name, topic(s) and timezone. Feel free to add anything else you feel is relevant.<br />
<br />
I'd invite anyone who wants to mentor new speakers to add their name as mentor as well.<br />
<br />
* Dave Cramer: Java and Postgresql, Logical Decoding, mentor<br />
* Jonathan Katz: SCRAM, PostgreSQL + Kubernetes, PostgreSQL 13, Range Types + Applications, Building an App with a bunch of Postgres features (Logical decoding, CTEs, functions, range types, etc.), Data Types<br />
* Stephen Frost: Security, PostgreSQL, other stuff<br />
* Keith Fiske: Partitioning, Extensions, Administration, PG History & Features, Monitoring<br />
* David Christensen: Replication, Bucardo, CTEs.<br />
* David Fetter: PostgreSQL as a control plane, Fun with Foreign Data Wrappers, Hacking for Beginners<br />
* Jennifer Scheuerell: Migrations, PostgreSQL and Django, mentor (Pacific time zone)<br />
* Harry Arroyo: PostgreSQL with Laravel, Django, Java, IT Security Expert, TI Mentor, Sysadmin, FullStack Developer, Hacker, App Developer (Android and iOS), DBA and other Stuff.<br />
* Jimmy Angelakos: PostgreSQL, performance, Full-Text Search, ETL with Python, Django (UK time zone)<br />
* Tomas Vondra: PostgreSQL, performance, various extensions, hacking, community stuff</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=34046PostgreSQL 12 Open Items2019-08-23T14:35:53Z<p>Fuzzycz: </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/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<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 />
* [https://www.postgresql.org/message-id/17827.1549866683%40sss.pgh.pa.us Undesirable PANIC on snapshot file open failure]<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 />
* [https://www.postgresql.org/message-id/20190801184333.GA21369@alvherre.pgsql index_rebuild_count in CLUSTER reporting never increments]<br />
<br />
== Decisions to Recheck Mid-Beta ==<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/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.<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 />
<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 12beta4 ===<br />
<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 />
<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 />
== 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: ???<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33863PostgreSQL 12 Open Items2019-08-04T21:43:34Z<p>Fuzzycz: </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/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<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 />
* [https://www.postgresql.org/message-id/aed6cc9f-98f3-2693-ac81-52bb0052307e%402ndquadrant.com postgresql.auto.conf file with duplicate entries not handled properly]<br />
* [https://www.postgresql.org/message-id/17827.1549866683%40sss.pgh.pa.us Undesirable PANIC on snapshot file open failure]<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 />
<br />
== Decisions to Recheck Mid-Beta ==<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/CAKcux6nZiO9-eEpr1ZD84bT1mBoVmeZkfont8iSpcmYrjhGWgA@mail.gmail.com getting ERROR "relation 16401 has no triggers" with partition foreign key alter]<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 />
<br />
=== Fixed issues ===<br />
<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 />
<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 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 />
<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 />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: June 20, 2019<br />
* beta3: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33851PostgreSQL 12 Open Items2019-07-30T18:13:01Z<p>Fuzzycz: </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/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<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 />
* [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 />
* [https://www.postgresql.org/message-id/aed6cc9f-98f3-2693-ac81-52bb0052307e%402ndquadrant.com postgresql.auto.conf file with duplicate entries not handled properly]<br />
* [https://www.postgresql.org/message-id/17827.1549866683%40sss.pgh.pa.us Undesirable PANIC on snapshot file open failure]<br />
<br />
== Decisions to Recheck Mid-Beta ==<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/CAKcux6nZiO9-eEpr1ZD84bT1mBoVmeZkfont8iSpcmYrjhGWgA@mail.gmail.com getting ERROR "relation 16401 has no triggers" with partition foreign key alter]<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 />
<br />
=== Fixed issues ===<br />
<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 />
<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 12beta3 ===<br />
<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 />
<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 />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: June 20, 2019<br />
* beta3: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33678PostgreSQL 12 Open Items2019-07-20T14:40:38Z<p>Fuzzycz: </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/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<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 />
* [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 />
* [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 />
* [https://www.postgresql.org/message-id/aed6cc9f-98f3-2693-ac81-52bb0052307e%402ndquadrant.com postgresql.auto.conf file with duplicate entries not handled properly]<br />
* [https://www.postgresql.org/message-id/17827.1549866683%40sss.pgh.pa.us Undesirable PANIC on snapshot file open failure]<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 />
* [https://www.postgresql.org/message-id/CA+u7OA5Hp0ra235F3czPom_FyAd-3+XwSJmX95r1+sRPOJc9VQ@mail.gmail.com REINDEX CONCURRENTLY causes ALTER TABLE to fail]<br />
<br />
== Decisions to Recheck Mid-Beta ==<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/20190618231233.GA27470@telsasoft.com Statistics with inheritance cause ANALYZE failures]<br />
** [https://www.postgresql.org/message-id/20190618235755.GA17759@telsasoft.com test case]<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 />
<br />
=== Fixed issues ===<br />
<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 />
<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 12beta3 ===<br />
<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 />
<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 />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: May 23, 2019<br />
* beta2: June 20, 2019<br />
* beta3: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33430PostgreSQL 12 Open Items2019-05-08T15:28:54Z<p>Fuzzycz: </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/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<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 />
* [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 />
* [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 />
* [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: Robest Haas<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/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<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 />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com|PG12, PGXS and linking pgfeutils]<br />
** Commit {{PgCommitURL|cc8d41511721d25d557fc02a46c053c0a602fed0}}, Author: Peter Eisentraut<br />
* [https://www.postgresql.org/message-id/CAD21AoB_+PSoO4J2dKEgy9qKf2uNnbHHOOSUcz6f20f-=T-bdg@mail.gmail.com vacuumdb and new VACUUM options]<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 />
** Commit {{PgCommitURL|a9c35cf85ca1ff72f16f0f10d7ddee6e582b62b8}}, Author: Andres Freund<br />
<br />
== Decisions to Recheck Mid-Beta ==<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 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/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** It's plausible, but not yet certain, that this is fixed in HEAD by {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** We may consider back-patching once that patch is a bit better tested<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Bug appears fixed as of {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
** Unfortunately, test cases show intermittent deadlocks, which we can't realistically fix now, so test cases will have to come out<br />
<br />
=== Fixed issues ===<br />
<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 />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<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 />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: XXX<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33425PostgreSQL 12 Open Items2019-05-07T19:29:08Z<p>Fuzzycz: </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/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<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 />
* [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 />
* [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 />
* [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: Robest Haas<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 />
* [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/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<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 />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com|PG12, PGXS and linking pgfeutils]<br />
** Commit {{PgCommitURL|cc8d41511721d25d557fc02a46c053c0a602fed0}}, Author: Peter Eisentraut<br />
<br />
== Decisions to Recheck Mid-Beta ==<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 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/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** It's plausible, but not yet certain, that this is fixed in HEAD by {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** We may consider back-patching once that patch is a bit better tested<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Bug appears fixed as of {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
** Unfortunately, test cases show intermittent deadlocks, which we can't realistically fix now, so test cases will have to come out<br />
<br />
=== Fixed issues ===<br />
<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 />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<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 />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: XXX<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_12_Open_Items&diff=33424PostgreSQL 12 Open Items2019-05-07T19:28:39Z<p>Fuzzycz: </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/21516.1552489217@sss.pgh.pa.us Debate INFO messages in ATTACH PARTITION and SET NOT NULL]<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 />
* [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 />
* [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 />
* [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: Robest Haas<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 />
* [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/23694.1556806002@sss.pgh.pa.us Inconsistent error message wording for REINDEX CONCURRENTLY]<br />
** Commit: {{PgCommitURL|5dc92b844e680c54a7ecd68de0ba53c949c3d605}}, Author: Michael Paquier, Owner: Peter Eisentraut<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 />
* [https://www.postgresql.org/message-id/16170.1557251214@sss.pgh.pa.us Leakage of predicate locks]<br />
* [https://www.postgresql.org/message-id/a912ffff-f6e4-778a-c86a-cf5c47a12933@2ndquadrant.com] PG12, PGXS and linking pgfeutils<br />
** Commit {{PgCommitURL|cc8d41511721d25d557fc02a46c053c0a602fed0}}, Author: Peter Eisentraut<br />
<br />
== Decisions to Recheck Mid-Beta ==<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 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/20190403063759.GF3298@paquier.xyz toast_tuple_target reloption doesn't work as expected]<br />
* [https://www.postgresql.org/message-id/20190416070119.GK2673@paquier.xyz Race conditions with checkpointer and shutdown]<br />
** It's plausible, but not yet certain, that this is fixed in HEAD by {{PgCommitURL|a1a789eb5ac894b4ca4b7742f2dc2d9602116e46}}<br />
** We may consider back-patching once that patch is a bit better tested<br />
* [https://www.postgresql.org/message-id/20190418011430.GA19133@paquier.xyz REINDEX INDEX on an index of pg_class can fail]<br />
** Bug appears fixed as of {{PgCommitURL|f912d7dec29341d55315fccef8dc3fdfd068c6e3}}<br />
** Unfortunately, test cases show intermittent deadlocks, which we can't realistically fix now, so test cases will have to come out<br />
<br />
=== Fixed issues ===<br />
<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 />
<br />
== Non-bugs ==<br />
<br />
== Resolved Issues ==<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 />
<br />
== Important Dates ==<br />
<br />
Current schedule:<br />
* feature freeze: April 7, 2019<br />
* beta1: XXX<br />
* beta2: XXX<br />
* rc1: XXX<br />
* ga: XXX<br />
<br />
[[Category:Open_Items]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PgCon_2019_Developer_Meeting&diff=33251PgCon 2019 Developer Meeting2019-04-08T17:42:39Z<p>Fuzzycz: </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 />
# Peter Geoghegan<br />
# Devrim Gündüz<br />
# Magnus Hagander<br />
# Amit Kapila<br />
# Jonathan Katz<br />
# Alexander Korotkov<br />
# Tom Lane<br />
# Heikki Linnakangas<br />
# Bruce Momjian<br />
# Dave Page<br />
# Tomas Vondra<br />
<br />
The following people will not be in Ottawa, and do not plan to attend:<br />
<br />
* Christoph Berg<br />
* Andreas Scherbaum<br />
<br />
== Agenda Items ==<br />
<br />
* 13.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 />
|- <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: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>Fuzzyczhttps://wiki.postgresql.org/index.php?title=FOSDEM/PGDay_2019_Developer_Meeting&diff=33000FOSDEM/PGDay 2019 Developer Meeting2019-02-01T08:32:12Z<p>Fuzzycz: </p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Thursday 31st January, 2019 at the Brussels Marriott Hotel, prior to FOSDEM/PGDay 2019. 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 10 and 11 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 />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Review the progress of the 12.0 schedule, and formulate plans to address any issues<br />
* Address any proposed timing, policy, or procedure issues<br />
* Address any proposed [http://en.wikipedia.org/wiki/Wicked_problem Wicked problems]<br />
* Commitfest Triage<br />
<br />
== Time & Location ==<br />
<br />
The meeting will be:<br />
<br />
* 9:00AM to 5:00PM<br />
* Brussels Marriott Hotel<br />
<br />
Coffee, tea and snacks will be served starting at 8:45am. Lunch will be provided.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname) and will be attending:<br />
<br />
* Christoph Berg<br />
* Joe Conway<br />
* Andres Freund<br />
* Stephen Frost<br />
* Daniel Gustafsson<br />
* Devrim Gündüz<br />
* Magnus Hagander<br />
* Álvaro Herrera<br />
* Amit Langote<br />
* Thomas Munro<br />
* Dave Page<br />
* Masahiko Sawada<br />
* Tomas Vondra<br />
* Gregory Stark<br />
<br />
The following people have sent their apologies:<br />
<br />
* Peter Eisentraut<br />
* Etsuro Fujita<br />
* Peter Geoghegan<br />
* Kyotaro Horiguchi<br />
* Tatsuo Ishii<br />
* Amit Kapila<br />
* Jonathan Katz<br />
* Tom Lane<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Craig Ringer<br />
* Simon Riggs, on holiday that week<br />
* Pavel Stehule<br />
<br />
==Photo==<br />
[[File:Fosdem-dev-meeting-2019.jpg|800px]]<br />
<br />
==Agenda Items==<br />
<br />
Please add agenda items here!<br />
<br />
* Communication between hackers and packagers (Devrim)<br />
* Bug tracking / Bug ID / Links to bug threads (Stephen, and Magnus, though he doesn't know it yet)<br />
* Contribution recognition (Stephen)<br />
* PGCon plans, and such (Stephen)<br />
* RMT for v12 (Stephen, plus whomever...)<br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:10<br />
|Welcome and introductions<br />
|Dave<br />
<br />
|- <br />
|09:10 - 09:20<br />
|12.0 Release Review<br />
|All<br />
<br />
|- <br />
|09:20 - 09:40<br />
|Communication between hackers and packagers<br />
|Devrim<br />
<br />
|- <br />
|09:40 - 10:00<br />
|Bug tracking / Bug ID / Links to bug threads<br />
|Stephen/.Magnus<br />
<br />
|- <br />
|10:00 - 10:20<br />
|Contribution recognition<br />
|Stephen<br />
<br />
|- <br />
|10:20 - 10:30<br />
|RMT for v12<br />
|Stephen<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 />
|PGCon plans and such<br />
|Stephen<br />
<br />
|- <br />
|11:15 - 12:30<br />
|???<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:30 - 13:30<br />
|Lunch<br />
|All<br />
<br />
|- <br />
|13:30 - 15:00<br />
|Commitfest Triage<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|15:00 - 15:30<br />
|Tea break<br />
|All<br />
<br />
|- <br />
|15:30 - 16:45<br />
|Commitfest Triage<br />
|All<br />
<br />
<br />
|- <br />
|16:45 - 17:00<br />
|Any other business<br />
|Dave<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|17:00<br />
|Finish<br />
|<br />
|}<br />
<br />
== Minutes ==<br />
<br />
<pre><br />
9.20: 12.0 Release Review<br />
==========================<br />
<br />
Dave: Are we on track, is there anything we want to change about the way we do the release?<br />
Andres: We should decide on a target date<br />
Stephen: We should do that the same as last year<br />
Andres: We had a lot of last minute questions about whether patches go in...<br />
Stephen: We should do some thinking about how to avoid that<br />
Magnus: Knowing the freeze window head of time would be good<br />
Greg: Then people will plan to put something in on the last day of the freeze<br />
Stephen: We would like it if people wouldn't put large patches in the last CF<br />
Dave: A problem since ... how many years?<br />
Andres: It's OK, we just kick them into the next CF (unready, new)<br />
Stephen: Triage this afternoon may help with that. What else could we do?<br />
Magnus: For a while we had placeholder patches that people put in so they wouldn't miss the cut-off. We should kill those.<br />
Stephen: The important thing is that we really do that. We had some cases where people felt very strongly that a patch wasn't ready but it went in.<br />
Andres: We need to escalate to other committers faster. We have other committers that only take a look at major patches after commit and then they find a lot of problems.<br />
Stephen: Problem is that when someone signs up no one else will look.<br />
Magnus: We need a way to detect the cases where something needs more committers to review.<br />
Stephen: How about: if a committer says that they have a concern then maybe the item goes on the "open items" list.<br />
Magnus: How about: if one committer objects, a new process that requires another committer to ...<br />
Joe: Perhaps there should be a wording you can use to say you want to block the patch until another couple of committers get involve to resolve the problem.<br />
Stephen: Commitfest status?<br />
Andres:<br />
Stephen: If someone commits after that status is set without a resolution process, then it becomes clear to everyone that it needs to be reverted, without complicated pain.<br />
Magnus: The problem is social, not technical. Let's start with the question of who triggers the process and how it gets resolved.<br />
Andres: Perhaps CCing core, as a documented process. Who can I contact?<br />
Greg: There is a risk of doing things in private.<br />
Stephen: It might go over better if something things are not discussed in public (ie reverting).<br />
Magnus: Technical problems should be addressed on hackers.<br />
Stephen: If we do it on on private lists we give people a chance to go back onto -hackers to discuss the technical question. Giving someone an opportunity to publicly reconsider and decide on their own that they want to revert it. private-committers is better than personal emails. We need a policy, and perhaps we could discuss it at pgcon. Who wants to take that action item?<br />
Everybody:<br />
Stephen: If nobody objects I will draft a policy and then we'll see if there are objections. There will be objections.<br />
Magnus: It makes sense to float something on the private committers list, before we get to pgcon. Let's not arrive there without a proposal.<br />
Andres: Discussing it before the next BF to raise awareness would be good.<br />
Stephen: I don't want to rush it, and come across as overbearing.<br />
Andres: Right but we don't have to agree on the policy, just discuss the ideas.<br />
Magnus: So people know that the issue exists.<br />
Stephen: It's on my list of things to do before pgcon. So basically by end of February. Good discussion, I will work up a draft policy and float it.<br />
<br />
Dave: We have a wiki section with procedures.<br />
Andres: The wiki is incredibly out of date.<br />
Magnus: It was also wrong when it wasn't out of date.<br />
Stephen: Some of the policies are on the website and some are on the wiki.<br />
Magnus: We should probably make the documentation scream at you when you're looking at an old version.<br />
Stephen: Policies about development should be in the docs in the source tree.<br />
Magnus: We should have a total index of policies that points to the docs, the wiki, ...<br />
Dave: We could have them in the docs so that they're in the source tree but publish them on the website with other policies.<br />
Andres: It does seem reasonable to have developer policies all in once place.<br />
Andres: The commitfest processs should be in there.<br />
Stephen: Action item for Andres.<br />
Dave: I'm going to remove stuff from the wiki into the website. It'll take that action point. Archives policy, ... and other ones that are more or less up to date. Those that are not up to date, I'll contact those people. Most of them are probably alright.<br />
<br />
Action points: Andres to document commitfest process. Dave to move stuff from wiki to website. Stephen to propose revert policy.<br />
<br />
9:59: Communication between hackers and packagers<br />
==================================================<br />
Devrim: There was a discussion about renaming a binary. We have to dig. I would ask the hackers to drop an email to the -packagers mailing list.<br />
Dave: I have annoyed people in the past by forgetting to tell people about changes to pgadmin.<br />
Stephen: What things need to go to packagers?<br />
Devrim: Andres did a great job of communicating with me about how to package the JIT stuff.<br />
Stephen: We can put that into a policy document. Tell us what things there are... changing binary names, removing things, new dependencies, ...<br />
Christoph: No body told me about the changes to the documentation build tools...<br />
Thomas: Could RMT add a sign-off step, "have we communicated all packaging changes?"<br />
Everybody: No!<br />
Christoph: Should we enable new features by default?<br />
Stephen: That is a whole other question...<br />
Stephen: Floating point dates were a case where the packagers made a choice that we didn't directly control.<br />
Greg: In cases where there is more than one option, like different SSL library implementations, we should leave that to packagers to do whatever is the preferred approach on that platform. Packagers have real policy decisions to make, they're not robots.<br />
Christoph: I had to rewrite pc_config in perl, to support cross compiling.<br />
Alvaro: As a committer, do I need to tell you if I change a binary name?<br />
Dave: Generally it's about knowing when changes are going to happen. Right now we have no coordination with Debian packages etc. I'd like to see us to things with more consistently. But we need to know when things are changing upstream. Adding a binary, etc.<br />
Devrim: Example: a while ago I had to add support for pg_basebackup.<br />
Thomas: Does this include header files that we export, and files like the errorcodes.txt?<br />
Magnus: Devrim needs to write a policy on this.<br />
Alvaro: Should we cross-post to -packagers?<br />
Magnus, Stephen: No! Devrim will give us a specific list of things that need to be send to -packagers.<br />
Christoph: For distributions other than RHEL and Debian, people may not even be following -hackers.<br />
Dave: packagers is not open because it has security information before the general public.<br />
Stephen: Do we need another mailing list for these announcements? More open?<br />
Stephen: Consolidate various other end-user lists?<br />
Dave: Devrim to propose policy to -hackers. Someone needs to start -packagers/-hackers discussion about communication.<br />
Christoph: I will.<br />
Devrim: I would like the PDFs to be built. Sometimes they break, but nobody notices upstream.<br />
Thomas: When the HTML build was OK?<br />
Devrim: Yes.<br />
Dave: Do we need to have the PDFs built on a build farm animal? Shall we ask Andrew to make that an option?<br />
<br />
Action points: Magnus to talk to Andrew. Devrim to propose communication policy document.<br />
<br />
10:30: Coffee.<br />
<br />
11:10: Bug tracking / Bug ID / Links to bug threads <br />
====================================================<br />
<br />
Thomas: Can we add clearer links to the pgadmin bug tracker from the bug reporting page?<br />
Greg: Could we have a drop list and forward bug reports to those projects?<br />
Thomas: Well at least a clearer link...<br />
Stephen: I like the combo box. Magnus?<br />
Greg: I wouldn't have a problem with the list having Advanced Server or RDS etc.<br />
Dave: Progressive reveal from a combo box, starting with a few options and adding more as we need them.<br />
Magnus: I don't think we should generate messages for other projects.<br />
Thomas: You could leave the mailing list at the centre but track the status.<br />
Christoph: You could extend the commitfest app to do that.<br />
Magnus: I have previously proposed that.<br />
Thomas: The problem is that threads started by email (not the form) don't have an ID.<br />
Dave: We own the mailing list software, so we could assign IDs to those.<br />
Stephen: I have previously proposed that.<br />
Christoph: The Wikipedia article for PostgreSQL notes that we have no bug tracker.<br />
Greg: There are a lot of -hackers threads by Tom that describe "known problems".<br />
Greg: I would like to compile a list of those emails.<br />
Thomas: User bugs are not the same as "known problems" like "if you do this and you do that the planner gets confused".<br />
Stephen: A link on the bug reporting problem to some known problems?<br />
Dave: If you have a real bug tracker you have to do triage.<br />
Stephen: We'd have to make sure that people can keep doing exactly what they're doing it today.<br />
Alvaro: Nathan Wagner runs a system that classifies bugs by reading the -bugs mailing list. I will write to the -hackers mailing list[1].<br />
Christoph: That could become part of the CF app.<br />
Stephen: Great, let's discuss this further on -hackers.<br />
<br />
Action points: Greg to report on "known problems" from the mail list.<br />
<br />
12:10: Contribution recognition <br />
================================<br />
<br />
Stephen: Robert and I have been doing reports on contributions. How do you think that's going?<br />
Andres: It's terrible. People don't get added to Major Contributors and are driven away from the project.<br />
Christoph: Right, I've been trying to get [redacted] put on the contributors list for years but have been told to take it up at pgcon.<br />
Dave: The problem is that no one wants to take responsiblity for it.<br />
Stephen: In the past Robert and I have done it at pgcon because core is there and they tell us to do it.<br />
Dave: I can't promise but there is no reason you can't email core during the year.<br />
Andres: You should write 'I am going to add this person in three days unless you object'.<br />
Joe: I think you should have more than Stephen and Robert proposing.<br />
Stephen: You don't think Robert and I disagree enough?<br />
Dave: We need a policy on who can be proposed (including non-backend code contributors?)<br />
Stephen: We need more people.<br />
Magnus: I would suggest someone with more of an outside perspective. I would suggest [redact].<br />
Daniel: We also have the difference between the release note contributors and the website contributors.<br />
Dave: Action item: add description <br />
<br />
Action points: Dave to write better descriptions of contributor classes. Dave to follow up on adding more people the team that deals with recognition.<br />
<br />
13:40: RMT<br />
===========<br />
<br />
Alvaro: We should have one again.<br />
Stephen: Should we define one before freeze.<br />
Alvaro: The first RMT had a set of rules, but it was so annoying that it was decided not to have rules; each release's RMT decides how it is going to operate.<br />
Andres: Last year there was a feature freeze + RMT announced in March.<br />
Stephen: The last RMT should share information with the next one.<br />
Andres: Should be more aggressive?<br />
<br />
13:50: PGCon<br />
=============<br />
<br />
Stephen: Feedback on who should be at the developer meeting in Ottawa?<br />
Stephen: What is the basis for limiting the list? Can we invite more?<br />
Dave: Room size is a problem.<br />
Dave: It's very good to have packagers in the meeting as we do today.<br />
Stephen: Perhaps we should decide what we're going to talk about and then decide who should be invited.<br />
Dave: Chicken and egg.<br />
Stephen: Dave and I will take an action point to look at past agendas and make sure we're getting the right people.<br />
<br />
Action points: Dave and Stephen to review past topics.<br />
<br />
14:10: Patch triage<br />
====================<br />
<br />
<discussion not recorded in minutes><br />
<br />
[1] https://www.postgresql.org/message-id/flat/201901311104.gwxzhzxu6ns6%40alvherre.pgsql<br />
</pre></div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=File:Fosdem-dev-meeting-2019.jpg&diff=32999File:Fosdem-dev-meeting-2019.jpg2019-02-01T08:24:21Z<p>Fuzzycz: </p>
<hr />
<div></div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=FOSDEM/PGDay_2019_Developer_Meeting&diff=32759FOSDEM/PGDay 2019 Developer Meeting2018-11-26T23:01:13Z<p>Fuzzycz: </p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Thursday 31st January, 2019 at the Brussels Marriott Hotel, prior to FOSDEM/PGDay 2019. 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 10 and 11 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 />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Review the progress of the 12.0 schedule, and formulate plans to address any issues<br />
* Address any proposed timing, policy, or procedure issues<br />
* Address any proposed [http://en.wikipedia.org/wiki/Wicked_problem Wicked problems]<br />
* Commitfest Triage<br />
<br />
== Time & Location ==<br />
<br />
The meeting will be:<br />
<br />
* 9:00AM to 5:00PM<br />
* Brussels Marriott Hotel<br />
<br />
Coffee, tea and snacks will be served starting at 8:45am. Lunch will be provided.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname) and will be attending:<br />
<br />
* Stephen Frost<br />
* Magnus Hagander<br />
* Thomas Munro<br />
* Dave Page<br />
* Tomas Vondra<br />
<br />
The following people have sent their apologies:<br />
<br />
* Peter Geoghegan<br />
* Kyotaro Horiguchi<br />
* Tatsuo Ishii<br />
* Amit Kapila<br />
* Jonathan Katz<br />
* Tom Lane<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Craig Ringer<br />
* Simon Riggs, on holiday that week<br />
* Pavel Stehule<br />
<br />
==Agenda Items==<br />
<br />
Please add agenda items here!<br />
<br />
* <br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:10<br />
|Welcome and introductions<br />
|Dave<br />
<br />
|- <br />
|09:10 - 09:20<br />
|12.0 Release Review<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:30 - 11:00<br />
|Coffee break<br />
|All<br />
<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:30 - 13:30<br />
|Lunch<br />
|All<br />
<br />
|- <br />
|13:30 - 15:00<br />
|Commitfest Triage<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|15:00 - 15:30<br />
|Tea break<br />
|All<br />
<br />
|- <br />
|15:30 - 16:45<br />
|Commitfest Triage<br />
|All<br />
<br />
<br />
|- <br />
|16:45 - 17:00<br />
|Any other business<br />
|Dave<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|17:00<br />
|Finish<br />
|<br />
|}<br />
<br />
== Minutes ==</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PgCon_2018_Developer_Meeting&diff=31526PgCon 2018 Developer Meeting2018-02-26T17:20:07Z<p>Fuzzycz: </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 />
* Joe Conway<br />
* Peter Eisentraut<br />
* Magnus Hagander<br />
* Tatsuo Ishii<br />
* Amit Kapila<br />
* Bruce Momjian<br />
* Thomas Munro<br />
* Michael Paquier<br />
* David Steele<br />
* Tomas Vondra<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>Fuzzyczhttps://wiki.postgresql.org/index.php?title=FOSDEM/PGDay_2018_Developer_Meeting&diff=31155FOSDEM/PGDay 2018 Developer Meeting2017-11-13T01:40:08Z<p>Fuzzycz: </p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Thursday 1st February, 2018 at the Brussels Marriott Hotel, prior to FOSDEM/PGDay 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 10 and 11 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 />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Review the progress of the 11.0 schedule, and formulate plans to address any issues<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 5:00PM<br />
* Brussels Marriott Hotel<br />
<br />
Coffee, tea and snacks will be served starting at 8:45am. Lunch will be provided.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname) and will be attending:<br />
<br />
* Magnus Hagander<br />
* Dave Page <br />
* Tomas Vondra<br />
<br />
The following people have sent their apologies:<br />
<br />
* KaiGai Kohei<br />
* Tom Lane<br />
* David Rowley<br />
<br />
==Agenda Items==<br />
<br />
Please add agenda items here!<br />
<br />
* 11.0 Release Review<br />
* Commitfest item review<br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:10<br />
|Welcome and introductions<br />
|Dave<br />
<br />
|- <br />
|09:10 - 09:20<br />
|10.0 Release Review<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:30 - 11:00<br />
|Coffee break<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:45 - 13:45<br />
|Lunch<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|15:00 - 15:30<br />
|Tea break<br />
|All<br />
<br />
|- <br />
|15:30 - 17:00<br />
|Open CommitFest Item Review<br />
|All<br />
<br />
|- <br />
|16:45 - 17:00<br />
|Any other business<br />
|Dave<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|17:00<br />
|Finish<br />
|<br />
|}<br />
<br />
== Minutes ==<br />
<br />
<pre><br />
Welcome<br />
--------<br />
<br />
Present: <br />
<br />
Apologies:<br />
<br />
11.0 Release Review<br />
-------------------<br />
<br />
<br />
None.<br />
</pre></div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=FOSDEM/PGDay_2017_Developer_Meeting&diff=29121FOSDEM/PGDay 2017 Developer Meeting2017-01-04T11:38:21Z<p>Fuzzycz: </p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Thursday 2nd February, 2017 at the Brussels Marriott Hotel, prior to FOSDEM/PGDay 2017. 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 9.6 and 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 />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Review the progress of the 10.0 schedule, and formulate plans to address any issues<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 5:00PM<br />
* Brussels Marriott Hotel<br />
<br />
Coffee, tea and snacks will be served starting at 8:45am. Lunch will be provided.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname) and will be attending:<br />
<br />
* Oleg Bartunov<br />
* Etsuro Fujita<br />
* Magnus Hagander<br />
* Petr Jelinek<br />
* Alexander Korotkov<br />
* Noah Misch<br />
* Bruce Momjian<br />
* Dave Page<br />
* Masahiko Sawada<br />
* Teodor Sigaev<br />
* Tomas Vondra<br />
<br />
The following people have sent their apologies:<br />
<br />
* Kyotaro Horiguchi<br />
* Tom Lane<br />
* Thomas Munro<br />
* Craig Ringer<br />
<br />
==Agenda Items==<br />
<br />
Please add agenda items here!<br />
<br />
==Agenda==<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Time<br />
!Item<br />
!Presenter<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|09:00 - 09:10<br />
|Welcome and introductions<br />
|Dave<br />
<br />
|- <br />
|09:10 - 09:30<br />
|10.0 Release Schedule<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|10:30 - 11:00<br />
|Coffee break<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|12:30 - 13:30<br />
|Lunch<br />
|All<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|15:00 - 15:30<br />
|Tea break<br />
|All<br />
<br />
|- <br />
|16:30 - 17:00<br />
|Any other business<br />
|Dave<br />
<br />
|- style="font-style:italic;background-color:lightgray;"<br />
|17:00<br />
|Finish<br />
|<br />
|}<br />
<br />
== Minutes ==</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PgConf.Asia_2016_Developer_Meeting&diff=28086PgConf.Asia 2016 Developer Meeting2016-08-24T15:35:36Z<p>Fuzzycz: /* RSVPs */</p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for the morning of Thursday 1st December, 2016 in Tokyo, prior to PGConf.Asia 2016. 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 9.6 release cycle. We have not invited any contributors based on their contributions to related projects, or seniority in regional user groups or sponsoring companies.<br />
<br />
The afternoon will be a Developer Unconference, open to a wider audience.<br />
<br />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Review the progress of the 10.0 schedule, and formulate plans to address any issues<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 event will be held on the fifth floor (using American/Japanese style counting) in room 5A at:<br />
<br />
Akihabara Convention Hall<br />
Akihabara Dai Bldig 4F 1-18-13 Sotokanda, <br />
Chiyoda-ku,<br />
Tokyo 101-0021, <br />
Japan<br />
<br />
Please see the [http://www.akibahall.jp/data/access_eng.html website] for details of how to reach the hall.<br />
<br />
The morning session (9AM - 12PM) will be used for a structured meeting, and the afternoon session (1PM - 5PM) will be used for a 2 track mini unconference for invitees to the morning session and other interested developers.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname) and will be attending:<br />
<br />
* Kyotaro Horiguchi<br />
* Kohei KaiGai<br />
* Dave Page<br />
* Michael Paquier<br />
* Simon Riggs<br />
* Masahiko Sawada<br />
* Teodor Sigaev<br />
* Tomas Vondra<br />
<br />
==Agenda==<br />
<br />
TBD<br />
<br />
==Agenda Items==<br />
<br />
Please list any agenda items below for inclusion on the schedule.<br />
* 10.0 Release Schedule</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=FOSDEM/PGDay_2016_Developer_Meeting&diff=26465FOSDEM/PGDay 2016 Developer Meeting2015-11-26T12:48:38Z<p>Fuzzycz: </p>
<hr />
<div>A meeting of the interested PostgreSQL developers is being planned for Thursday 28th January, 2016 at the Brussels Marriott Hotel, prior to FOSDEM/PGDay 2016. 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 9.5 release cycle. We have not invited any contributors based on their contributions to related projects, or seniority in regional user groups or sponsoring companies.<br />
<br />
This is a PostgreSQL Community event.<br />
<br />
== Meeting Goals ==<br />
<br />
* Review the progress of the 9.6 schedule, and formulate plans to address any issues<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 5:30PM<br />
* Brussels Marriott Hotel<br />
<br />
Coffee, tea and snacks will be served starting at 8:45am. Lunch will be provided.<br />
<br />
== RSVPs ==<br />
<br />
The following people have RSVPed to the meeting (in alphabetical order, by surname) and will be attending:<br />
<br />
* Magnus Hagander<br />
* Petr Jelinek<br />
* Peter Geoghegan<br />
* Tom Lane<br />
* Bruce Momjian<br />
* Dave Page<br />
* Tomas Vondra<br />
<br />
The following people have sent their apologies:<br />
<br />
* Josh Berkus<br />
* Andrew Dunstan<br />
* Stephen Frost<br />
* Amit Kapila<br />
* Robert Haas<br />
* Michael Paquier<br />
<br />
==Agenda Items==<br />
<br />
Please list any agenda items below for inclusion on the schedule.</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2015&diff=26382PostgreSQL Conference Europe Talks 20152015-11-11T18:23:09Z<p>Fuzzycz: /* Thursday */</p>
<hr />
<div><br />
pgconf.eu 2015 took place in Vienna, Austria, from 2015-10-27 to 2015-10-30.<br />
<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 || [http://snowman.net/pgconfeu PostgreSQL Server Development]<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 || [http://tamaraatanasoska.github.io/notes/more-than-just-code-:-the-bigger-picture/ 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 || [[media:PGCONF-PITR Mark Jones 2015-10-28.pdf|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 || [https://wiki.postgresql.org/images/4/4e/Createam.pdf 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 || [http://slides.com/apatheticmagpie/managing-postgres-with-ansible 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 || [https://drive.google.com/open?id=0B7woI_p7A5NkOG1yZTloT0VabXM HA strategy, properly done]<br />
|+<br />
| 16:20 - 17:10 || Palais I-III || Jan Holčapek || [http://www.slideshare.net/holcapek/lets-turn-your-postgresql-into-columnar-store-with-cstorefdw Let’s turn your PostgreSQL into columnar store with cstore_fdw]<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 || [http://www.slideshare.net/fuzzycz/performance-improvements-in-postgresql-95-and-beyond 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 || [[Media: 2015-rybak-orq.pdf|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 || [https://docs.google.com/viewer?a=v&pid=sites&srcid=ZGVmYXVsdGRvbWFpbnxyb2JlcnRtaGFhc3xneDo1ZmFhYzBhNjNhNzVhMDM0 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 || [[Media:Becoming_A_SQL_Guru.pdf| 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 || [http://www.slideshare.net/PostgreSQL-Consulting/linux-tuning-to-improve-postgresql-performance 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 || [http://www.slideshare.net/fuzzycz/postgresql-on-ext4-xfs-btrfs-and-zfs-54525451 PostgreSQL Performance on EXT4, XFS, F2FS, BTRFS and ZFS]<br />
|+<br />
| 15:40 - 16:30 || Palais I-III || Anastasia Lubennikova || [http://www.slideshare.net/AnastasiaLubennikova/indexes-dont-mean-slow-inserts Indexes don't mean slow inserts.]<br />
|+<br />
| 17:00 - 17:50 || Ballroom A+B+C+D || Harald Armin Massa || Lightning Talks:<br/><br />
[https://wiki.postgresql.org/images/9/95/Stephen_Frost_-_Website_2015-10-29.pdf Stephen Frost - Website]<br/><br />
Andreas Scherbaum - State of the Icecream<br/><br />
[https://wiki.postgresql.org/images/2/20/Ildus_Kurbangaliev_-_Monitoring_of_Waits.pdf Ildus Kurbangaliev - Waits monitoring in PostgreSQL]<br/><br />
[https://wiki.postgresql.org/images/8/8f/Marco_Slot_-_pg_paxos_2015-10-29.pdf Marco Slot - pg_paxos]<br/><br />
[https://wiki.postgresql.org/images/2/28/Feike_Steenbergen_-_Patroni_2015-10-29.pdf Feike Steenbergen - Patroni]<br/><br />
[https://wiki.postgresql.org/images/1/10/Rafael_Martinez_Guerrero_-_PgBackMan_2015-10-29.pdf Rafael Martinez Guerrero - PgBackMan]<br/><br />
Konstantin Knizhnik - DTM<br/><br />
[https://wiki.postgresql.org/images/e/e0/Pgconfeu2015mba.pdf Michael Banck - 8.4 for Debian]<br/><br />
Greg Stark - VAX<br/><br />
[https://wiki.postgresql.org/images/5/5b/Pavan_Deolasee_-_Postgres_XL_9.5_2015-10-29.pdf Pavan Deolasee - Postgres XL 9.5]<br/><br />
Petr Jelinek - pglogical<br/><br />
[https://wiki.postgresql.org/images/1/1b/Valentine_Gogichashvili_-_psycopg2_Replication.pdf Valentine Gogichashvili - psycopg2 Replication]<br/><br />
[https://wiki.postgresql.org/images/a/ac/Giuseppe_Broccolo_-_Extending_BRIN_Indexes_2015-10-29.pdf Giuseppe Broccolo - Extending BRIN Indexes]<br/><br />
[https://wiki.postgresql.org/images/6/68/Aliaksandr_Aliashkevich_%28Sasha%29_-_Data_Visualisation_2015-10-29.pdf Aliaksandr Aliashkevich - Data Visualisation]<br/><br />
Manuel Kniep - pgbundle<br/><br />
[https://wiki.postgresql.org/images/e/ef/Dr._Ernst-Georg_Schmid_-_Slice_and_Dice_2015-10-29.pdf Dr. Ernst-Georg Schmid - Slice and Dice]<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 || [http://www.slideshare.net/PostgreSQL-Consulting/autovacuum-explained-for-engineers-new-improved-version-pgconfeu-2015-vienna 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 || [https://sites.google.com/site/robertmhaas/presentations/The%20Elephants%20in%20the%20Room%20-%20PGConf%20EU%202015.odp?attredirects=0&d=1 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>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2015&diff=26381PostgreSQL Conference Europe Talks 20152015-11-11T18:22:42Z<p>Fuzzycz: /* Wednesday */</p>
<hr />
<div><br />
pgconf.eu 2015 took place in Vienna, Austria, from 2015-10-27 to 2015-10-30.<br />
<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 || [http://snowman.net/pgconfeu PostgreSQL Server Development]<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 || [http://tamaraatanasoska.github.io/notes/more-than-just-code-:-the-bigger-picture/ 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 || [[media:PGCONF-PITR Mark Jones 2015-10-28.pdf|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 || [https://wiki.postgresql.org/images/4/4e/Createam.pdf 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 || [http://slides.com/apatheticmagpie/managing-postgres-with-ansible 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 || [https://drive.google.com/open?id=0B7woI_p7A5NkOG1yZTloT0VabXM HA strategy, properly done]<br />
|+<br />
| 16:20 - 17:10 || Palais I-III || Jan Holčapek || [http://www.slideshare.net/holcapek/lets-turn-your-postgresql-into-columnar-store-with-cstorefdw Let’s turn your PostgreSQL into columnar store with cstore_fdw]<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 || [http://www.slideshare.net/fuzzycz/performance-improvements-in-postgresql-95-and-beyond 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 || [[Media: 2015-rybak-orq.pdf|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 || [https://docs.google.com/viewer?a=v&pid=sites&srcid=ZGVmYXVsdGRvbWFpbnxyb2JlcnRtaGFhc3xneDo1ZmFhYzBhNjNhNzVhMDM0 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 || [[Media:Becoming_A_SQL_Guru.pdf| 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 || [http://www.slideshare.net/PostgreSQL-Consulting/linux-tuning-to-improve-postgresql-performance 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 || [http://www.slideshare.net/AnastasiaLubennikova/indexes-dont-mean-slow-inserts Indexes don't mean slow inserts.]<br />
|+<br />
| 17:00 - 17:50 || Ballroom A+B+C+D || Harald Armin Massa || Lightning Talks:<br/><br />
[https://wiki.postgresql.org/images/9/95/Stephen_Frost_-_Website_2015-10-29.pdf Stephen Frost - Website]<br/><br />
Andreas Scherbaum - State of the Icecream<br/><br />
[https://wiki.postgresql.org/images/2/20/Ildus_Kurbangaliev_-_Monitoring_of_Waits.pdf Ildus Kurbangaliev - Waits monitoring in PostgreSQL]<br/><br />
[https://wiki.postgresql.org/images/8/8f/Marco_Slot_-_pg_paxos_2015-10-29.pdf Marco Slot - pg_paxos]<br/><br />
[https://wiki.postgresql.org/images/2/28/Feike_Steenbergen_-_Patroni_2015-10-29.pdf Feike Steenbergen - Patroni]<br/><br />
[https://wiki.postgresql.org/images/1/10/Rafael_Martinez_Guerrero_-_PgBackMan_2015-10-29.pdf Rafael Martinez Guerrero - PgBackMan]<br/><br />
Konstantin Knizhnik - DTM<br/><br />
[https://wiki.postgresql.org/images/e/e0/Pgconfeu2015mba.pdf Michael Banck - 8.4 for Debian]<br/><br />
Greg Stark - VAX<br/><br />
[https://wiki.postgresql.org/images/5/5b/Pavan_Deolasee_-_Postgres_XL_9.5_2015-10-29.pdf Pavan Deolasee - Postgres XL 9.5]<br/><br />
Petr Jelinek - pglogical<br/><br />
[https://wiki.postgresql.org/images/1/1b/Valentine_Gogichashvili_-_psycopg2_Replication.pdf Valentine Gogichashvili - psycopg2 Replication]<br/><br />
[https://wiki.postgresql.org/images/a/ac/Giuseppe_Broccolo_-_Extending_BRIN_Indexes_2015-10-29.pdf Giuseppe Broccolo - Extending BRIN Indexes]<br/><br />
[https://wiki.postgresql.org/images/6/68/Aliaksandr_Aliashkevich_%28Sasha%29_-_Data_Visualisation_2015-10-29.pdf Aliaksandr Aliashkevich - Data Visualisation]<br/><br />
Manuel Kniep - pgbundle<br/><br />
[https://wiki.postgresql.org/images/e/ef/Dr._Ernst-Georg_Schmid_-_Slice_and_Dice_2015-10-29.pdf Dr. Ernst-Georg Schmid - Slice and Dice]<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 || [http://www.slideshare.net/PostgreSQL-Consulting/autovacuum-explained-for-engineers-new-improved-version-pgconfeu-2015-vienna 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 || [https://sites.google.com/site/robertmhaas/presentations/The%20Elephants%20in%20the%20Room%20-%20PGConf%20EU%202015.odp?attredirects=0&d=1 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>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Unconference&diff=24911PgCon 2015 Developer Unconference2015-06-09T21:46:36Z<p>Fuzzycz: /* 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 />
* Stephen Frost<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Álvaro Herrera<br />
* Stefan Kaltenbrunner<br />
* Amit Kapila<br />
* Konstantin Knizhnik<br />
* Alexander Korotkov<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
* Grant McAlister<br />
* Noah Misch<br />
* Jim Nasby<br />
* Dave Page<br />
* Magnus Hagander<br />
* Kumar Rajeev Rastogi<br />
* Greg Smith<br />
* KaiGai Kohei<br />
* Tomas Vondra<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<br />
<br />
|- style="background-color:lightgray;"<br />
|Infrastructure Q&A<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander<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<br />
<br />
|- style="background-color:lightgray;"<br />
|Vertical Scalability w.r.t Writes<br />
|Open<br />
|<br />
|Amit Kapila<br />
|Greg Smith, Hannu Valtonen, Ilya Kosmodemiansky, Tomas Vondra<br />
<br />
|- style="background-color:lightgray;"<br />
|Security Team Meeting<br />
|Closed<br />
|<br />
|Heikki Linnakangas, Stephen Frost, Magnus Hagander<br />
|Noah Misch<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Compilation + LLVM<br />
|Open<br />
|<br />
|Kumar Rajeev Rastogi<br />
|Jeff Davis, Tomas Vondra<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<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<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<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 />
|Tomas Vondra<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<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<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Slony Development]]<br />
|Open<br />
|<br />
| Steve Singer, Chris Browne, Jan Wieck<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 />
== Security Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<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</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PgCon_2015_Developer_Unconference&diff=24910PgCon 2015 Developer Unconference2015-06-09T21:32:56Z<p>Fuzzycz: /* 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 />
* Stephen Frost<br />
* Kevin Grittner<br />
* Robert Haas<br />
* Álvaro Herrera<br />
* Stefan Kaltenbrunner<br />
* Amit Kapila<br />
* Konstantin Knizhnik<br />
* Alexander Korotkov<br />
* Ilya Kosmodemiansky<br />
* Amit Langote<br />
* Grant McAlister<br />
* Noah Misch<br />
* Jim Nasby<br />
* Dave Page<br />
* Magnus Hagander<br />
* Kumar Rajeev Rastogi<br />
* Greg Smith<br />
* KaiGai Kohei<br />
* Tomas Vondra<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<br />
<br />
|- style="background-color:lightgray;"<br />
|Infrastructure Q&A<br />
|Open<br />
|<br />
|Dave Page, Stephen Frost, Stefan Kaltenbrunner, Magnus Hagander<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<br />
<br />
|- style="background-color:lightgray;"<br />
|Vertical Scalability w.r.t Writes<br />
|Open<br />
|<br />
|Amit Kapila<br />
|Greg Smith, Hannu Valtonen, Ilya Kosmodemiansky<br />
<br />
|- style="background-color:lightgray;"<br />
|Security Team Meeting<br />
|Closed<br />
|<br />
|Heikki Linnakangas, Stephen Frost, Magnus Hagander<br />
|Noah Misch<br />
<br />
|- style="background-color:lightgray;"<br />
|Native Compilation + LLVM<br />
|Open<br />
|<br />
|Kumar Rajeev Rastogi<br />
|Jeff Davis<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<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<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<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 />
|<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<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<br />
<br />
|- style="background-color:lightgray;"<br />
|[[PgCon2015ClusterSummit|Slony Development]]<br />
|Open<br />
|<br />
| Steve Singer, Chris Browne, Jan Wieck<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 />
== Security Team Meeting ==<br />
<br />
=== Meeting Notes ===<br />
* To be filled in<br />
<br />
=== Attendees ===<br />
* To be filled in<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</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=24019PostgreSQL Conference Europe Talks 20142014-12-22T18:35:44Z<p>Fuzzycz: </p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
* Rendimiento: el bueno, el malo y el feo, Álvaro Herrera<br />
<br />
=== Medici III ===<br />
<br />
* [http://www.joeconway.com/presentations/migrating-pgconf.eu.2014.pdf Migration to PostgreSQL], Joe Conway, Michael Meskes<br />
* [http://www.slideshare.net/nosys/using-postgre-sqljavapgcon2014 PostgreSQL and Java: best practices] + [https://github.com/8kdata/javapostgres Source code] ([https://twitter.com/ahachete Álvaro Hernández])<br />
<br />
=== Renacimiento I ===<br />
<br />
* Data analysis, Hans-Jürgen Schönig<br />
* [https://wiki.postgresql.org/images/d/de/NoSQL_training_-_pgconf.eu.pdf NoSQL on Acid – Maximizing Results with JSONB and PostgreSQL], Bruce Momjian, Thom Brown<br />
<br />
=== Florencia II ===<br />
<br />
* PostgreSQL Backups, Replication & Disaster Recovery, Simon Riggs<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Keynote ===<br />
<br />
* Not Only NoSQL: A Case for NoSQL + PostgreSQL in a Big Data World, Matt Asay<br />
<br />
=== Medici I ===<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)], Alexey Klyukin<br />
<br />
* [http://www.hagander.net/talks/postgresql94_2.pdf What's new in PostgreSQL 9.4], Magnus Hagander<br />
<br />
* [http://www.joeconway.com/presentations/test-pres-pgconf.eu.2014.pdf Who's the Fairest of Them All? Postgres Interface Performance], Joe Conway<br />
<br />
* [http://momjian.us/main/presentations/overview.html#scaling Postgres Scaling Opportunities], Bruce Momjian<br />
<br />
* Row Level Security, Stephen Frost<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III (Spanish track) ===<br />
<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure], Rafael Martinez Guerrero<br />
<br />
* Desmitificando la búsqueda de Postgresql, Javier ramirez<br />
<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS], Alejandro E. Brito Monedero<br />
<br />
* Características para Inteligencia de Negocios en Postgres, Álvaro Herrera<br />
<br />
* Almacenamiento de archivos en PostgreSQL: pros y contras, Martín Marqués<br />
<br />
* Domando a la bestia "replicación", Jaime Casanova<br />
<br />
=== Renacimiento I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]], Gabrielle Roth<br />
<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] ([http://www.slideshare.net/fuzzycz/performance-archaeology-40583681 slideshare]), Tomas Vondra<br />
<br />
* [[Media: Udr-pgconf.pdf|UDR - Uni Directional Replication]], Petr Jelinek<br />
<br />
* [http://www.dalibo.org/_media/opm_talk_en.pdf OPM - Open PostgreSQL Monitoring], Jean-Paul Argudo and Julien Rouhaud<br />
<br />
* Choosing the right filesystem for PostgreSQL, Devrim GÜNDÜZ<br />
<br />
* [http://tapoueh.org/images/confs/PGCONF_EU_2014_backups.pdf You'd better have tested backups...], [http://tapoueh.org/confs Dimitri Fontaine]<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* CartoDB: Empowering dynamic mapping with PostgreSQL, Alejandro Martínez<br />
<br />
* [http://michael.otacoo.com/content/materials/20140919_pgopen_logirep.pdf Understanding logical decoding and replication], Michael Paquier<br />
<br />
* [http://momjian.us/main/presentations/features.html#indexing Flexible Indexing with Postgres], Bruce Momjian<br />
<br />
* [http://gianni.people.2ndquadrant.com/home/formalising-sql-in-higher-order-logic Formalising SQL in Higher-Order Logic], Gianni Ciolli, Marco Maggesi<br />
<br />
* Locks unpicked, Álvaro Herrera, Simon Riggs<br />
<br />
* Analytical PostgreSQL -- Ordered set aggregates and Grouping Sets, Atri Sharma<br />
<br />
=== Medici III ===<br />
<br />
* [http://gauss.credativ.com/~mme/2014/PGConf_EU_2014_V01.pdf Open Source - A Blessing Or A Curse?], Michael Meskes<br />
<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News], Vincent Picavet<br />
<br />
* [https://cloud.cosmos.esa.int/public.php?service=files&t=f5b1a1a950c6fffd10d164f3e42725cd&download Ruling the Galaxy with PostgreSQL: Stories from the ESA Gaia Archive], Juan Gonzalez Nunez<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment], Jim Mlodgenski<br />
<br />
* How we fixed bugs and rescued data, Harald Armin Massa<br />
<br />
=== Renacimiento I ===<br />
<br />
* [http://tapoueh.org/images/confs/PGCONF_EU_2014_pgloader.pdf Loading data in PostgreSQL, Fast. Any Data.], [http://tapoueh.org/ Dimitri Fontaine]<br />
<br />
* Advanced Authentication, Stephen Frost<br />
<br />
* [http://thebuild.com/presentations/corruption-pgconfeu-2014.pdf Finding and Repairing Data Corruption], Christophe Pettus<br />
<br />
* [https://docs.google.com/presentation/d/1gJL93iGNxbo9B2Y2sVnWVQfPBGllEjtoZlp6UitUwXM/edit?usp=sharing Scaling fashionably: From Startup to Scale at Zalando], Valentine Gogichashvili<br />
<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool], Kaarel Moppel<br />
<br />
* [https://speakerdeck.com/lfittl/advanced-pg-stat-statements-filtering-regression-testing-and-more Advanced Use of pg_stat_statements: Filtering, Regression Testing & more], Lukas Fittl<br />
<br />
=== Lightning Talks ===<br />
<br />
* [http://tapoueh.org/images/confs/PGCONF_EU_2014_pgcharts.pdf Turn your SQL query into Charts], [http://tapoueh.org Dimitri Fontaine]<br />
* [https://drive.google.com/file/d/0B-SFRgngatN_alhyWmZDdHRFcjQ/view?usp=sharing map()/reduce() with PostgreSQL + PL/Proxy], Ernst-Georg Schmid<br />
<br />
* [https://alioth.debian.org/scm/loggerhead/pkg-postgresql/postgresql-common/trunk/files postgresql-common for Red Hat], Jens Wilke<br />
<br />
* [https://perdomo.me/presentations/Immutable-DB.pdf A quest for an Immutable DB], Iván Perdomo<br />
<br />
* [[Media: Pgpass_pgconfeu_groth.pdf|Adventures in Ridiculous Benchmarking: pgpass]], Gabrielle Roth<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [https://github.com/Su-Shee/talks Database Unit Testing with PgTAP], Susanne Schmidt<br />
<br />
* Common difficulties for new PostgreSQL users - and what we can do about them, Craig Ringer<br />
<br />
* Hacking PostgreSQL, Stephen Frost<br />
<br />
* [https://github.com/akorotkov/talks/raw/master/pgconfeu-2014-jsquery.pdf Jsquery - the jsonb query language with GIN indexing support], Alexander Korotkov<br />
<br />
=== Medici III ===<br />
<br />
* [http://www.slideshare.net/oseemann/scaling-a-saas-backend-with-postgresql-a-case-study Scaling a SaaS backend with PostgreSQL], Oliver Seemann<br />
<br />
* [https://wiki.postgresql.org/wiki/File:RDS_EUPostgres2014_final.pptx Amazon RDS for PostgreSQL], Grant McAlister<br />
<br />
* [http://www.slideshare.net/8kdata/toro-db-pgconfeu2014 ToroDB: a new, open-source, document-oriented, JSON database, built on Postgres], [https://twitter.com/ahachete Álvaro Hernández]<br />
<br />
* Submitting a proper Postgres bug report, Jon Erdman<br />
<br />
=== Renaciemiento I ===<br />
<br />
* [http://andres.people.2ndquadrant.com/pgconf-eu-2014-10-23/bdr.pdf BDR - Asynchronous multimaster for postgres], Andres Freund<br />
<br />
* [http://thebuild.com/presentations/backups-pgconfeu-2014.pdf Be Very Afraid: Disaster Planning and Recovery], Christophe Pettus<br />
<br />
* [http://gianni.people.2ndquadrant.com/home/logical-decoding-for-auditing Logical Decoding for Auditing], Gianni Ciolli<br />
<br />
* walbouncer: Filtering the PostgreSQL transaction log, Hans-Jürgen Schönig<br />
<br />
=== Keynotes ===<br />
<br />
* NoSQL on Acid – Maximizing Results With JSONB And PostgreSQL, Keith Alsheimer<br />
<br />
* PostgreSQL Odyssey at 88mph, Simon Riggs<br />
<br />
* [https://github.com/trustly/keynotes/raw/master/PgConf%202014%20Trustly.pdf How we use PostgreSQL at Trustly], Joel Jacobson<br />
<br />
* Closing Session, Dave Page, Magnus Hagander</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=24018PostgreSQL Conference Europe Talks 20142014-12-22T18:33:56Z<p>Fuzzycz: </p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
* Rendimiento: el bueno, el malo y el feo, Álvaro Herrera<br />
<br />
=== Medici III ===<br />
<br />
* [http://www.joeconway.com/presentations/migrating-pgconf.eu.2014.pdf Migration to PostgreSQL], Joe Conway, Michael Meskes<br />
* [http://www.slideshare.net/nosys/using-postgre-sqljavapgcon2014 PostgreSQL and Java: best practices] + [https://github.com/8kdata/javapostgres Source code] ([https://twitter.com/ahachete Álvaro Hernández])<br />
<br />
=== Renacimiento I ===<br />
<br />
* Data analysis, Hans-Jürgen Schönig<br />
* [https://wiki.postgresql.org/images/d/de/NoSQL_training_-_pgconf.eu.pdf NoSQL on Acid – Maximizing Results with JSONB and PostgreSQL], Bruce Momjian, Thom Brown<br />
<br />
=== Florencia II ===<br />
<br />
* PostgreSQL Backups, Replication & Disaster Recovery, Simon Riggs<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Keynote ===<br />
<br />
* Not Only NoSQL: A Case for NoSQL + PostgreSQL in a Big Data World, Matt Asay<br />
<br />
=== Medici I ===<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)], Alexey Klyukin<br />
<br />
* [http://www.hagander.net/talks/postgresql94_2.pdf What's new in PostgreSQL 9.4], Magnus Hagander<br />
<br />
* [http://www.joeconway.com/presentations/test-pres-pgconf.eu.2014.pdf Who's the Fairest of Them All? Postgres Interface Performance], Joe Conway<br />
<br />
* [http://momjian.us/main/presentations/overview.html#scaling Postgres Scaling Opportunities], Bruce Momjian<br />
<br />
* Row Level Security, Stephen Frost<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III (Spanish track) ===<br />
<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure], Rafael Martinez Guerrero<br />
<br />
* Desmitificando la búsqueda de Postgresql, Javier ramirez<br />
<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS], Alejandro E. Brito Monedero<br />
<br />
* Características para Inteligencia de Negocios en Postgres, Álvaro Herrera<br />
<br />
* Almacenamiento de archivos en PostgreSQL: pros y contras, Martín Marqués<br />
<br />
* Domando a la bestia "replicación", Jaime Casanova<br />
<br />
=== Renacimiento I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]], Gabrielle Roth<br />
<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] ([http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|slideshare]), Tomas Vondra<br />
<br />
* [[Media: Udr-pgconf.pdf|UDR - Uni Directional Replication]], Petr Jelinek<br />
<br />
* [http://www.dalibo.org/_media/opm_talk_en.pdf OPM - Open PostgreSQL Monitoring], Jean-Paul Argudo and Julien Rouhaud<br />
<br />
* Choosing the right filesystem for PostgreSQL, Devrim GÜNDÜZ<br />
<br />
* [http://tapoueh.org/images/confs/PGCONF_EU_2014_backups.pdf You'd better have tested backups...], [http://tapoueh.org/confs Dimitri Fontaine]<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* CartoDB: Empowering dynamic mapping with PostgreSQL, Alejandro Martínez<br />
<br />
* [http://michael.otacoo.com/content/materials/20140919_pgopen_logirep.pdf Understanding logical decoding and replication], Michael Paquier<br />
<br />
* [http://momjian.us/main/presentations/features.html#indexing Flexible Indexing with Postgres], Bruce Momjian<br />
<br />
* [http://gianni.people.2ndquadrant.com/home/formalising-sql-in-higher-order-logic Formalising SQL in Higher-Order Logic], Gianni Ciolli, Marco Maggesi<br />
<br />
* Locks unpicked, Álvaro Herrera, Simon Riggs<br />
<br />
* Analytical PostgreSQL -- Ordered set aggregates and Grouping Sets, Atri Sharma<br />
<br />
=== Medici III ===<br />
<br />
* [http://gauss.credativ.com/~mme/2014/PGConf_EU_2014_V01.pdf Open Source - A Blessing Or A Curse?], Michael Meskes<br />
<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News], Vincent Picavet<br />
<br />
* [https://cloud.cosmos.esa.int/public.php?service=files&t=f5b1a1a950c6fffd10d164f3e42725cd&download Ruling the Galaxy with PostgreSQL: Stories from the ESA Gaia Archive], Juan Gonzalez Nunez<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment], Jim Mlodgenski<br />
<br />
* How we fixed bugs and rescued data, Harald Armin Massa<br />
<br />
=== Renacimiento I ===<br />
<br />
* [http://tapoueh.org/images/confs/PGCONF_EU_2014_pgloader.pdf Loading data in PostgreSQL, Fast. Any Data.], [http://tapoueh.org/ Dimitri Fontaine]<br />
<br />
* Advanced Authentication, Stephen Frost<br />
<br />
* [http://thebuild.com/presentations/corruption-pgconfeu-2014.pdf Finding and Repairing Data Corruption], Christophe Pettus<br />
<br />
* [https://docs.google.com/presentation/d/1gJL93iGNxbo9B2Y2sVnWVQfPBGllEjtoZlp6UitUwXM/edit?usp=sharing Scaling fashionably: From Startup to Scale at Zalando], Valentine Gogichashvili<br />
<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool], Kaarel Moppel<br />
<br />
* [https://speakerdeck.com/lfittl/advanced-pg-stat-statements-filtering-regression-testing-and-more Advanced Use of pg_stat_statements: Filtering, Regression Testing & more], Lukas Fittl<br />
<br />
=== Lightning Talks ===<br />
<br />
* [http://tapoueh.org/images/confs/PGCONF_EU_2014_pgcharts.pdf Turn your SQL query into Charts], [http://tapoueh.org Dimitri Fontaine]<br />
* [https://drive.google.com/file/d/0B-SFRgngatN_alhyWmZDdHRFcjQ/view?usp=sharing map()/reduce() with PostgreSQL + PL/Proxy], Ernst-Georg Schmid<br />
<br />
* [https://alioth.debian.org/scm/loggerhead/pkg-postgresql/postgresql-common/trunk/files postgresql-common for Red Hat], Jens Wilke<br />
<br />
* [https://perdomo.me/presentations/Immutable-DB.pdf A quest for an Immutable DB], Iván Perdomo<br />
<br />
* [[Media: Pgpass_pgconfeu_groth.pdf|Adventures in Ridiculous Benchmarking: pgpass]], Gabrielle Roth<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [https://github.com/Su-Shee/talks Database Unit Testing with PgTAP], Susanne Schmidt<br />
<br />
* Common difficulties for new PostgreSQL users - and what we can do about them, Craig Ringer<br />
<br />
* Hacking PostgreSQL, Stephen Frost<br />
<br />
* [https://github.com/akorotkov/talks/raw/master/pgconfeu-2014-jsquery.pdf Jsquery - the jsonb query language with GIN indexing support], Alexander Korotkov<br />
<br />
=== Medici III ===<br />
<br />
* [http://www.slideshare.net/oseemann/scaling-a-saas-backend-with-postgresql-a-case-study Scaling a SaaS backend with PostgreSQL], Oliver Seemann<br />
<br />
* [https://wiki.postgresql.org/wiki/File:RDS_EUPostgres2014_final.pptx Amazon RDS for PostgreSQL], Grant McAlister<br />
<br />
* [http://www.slideshare.net/8kdata/toro-db-pgconfeu2014 ToroDB: a new, open-source, document-oriented, JSON database, built on Postgres], [https://twitter.com/ahachete Álvaro Hernández]<br />
<br />
* Submitting a proper Postgres bug report, Jon Erdman<br />
<br />
=== Renaciemiento I ===<br />
<br />
* [http://andres.people.2ndquadrant.com/pgconf-eu-2014-10-23/bdr.pdf BDR - Asynchronous multimaster for postgres], Andres Freund<br />
<br />
* [http://thebuild.com/presentations/backups-pgconfeu-2014.pdf Be Very Afraid: Disaster Planning and Recovery], Christophe Pettus<br />
<br />
* [http://gianni.people.2ndquadrant.com/home/logical-decoding-for-auditing Logical Decoding for Auditing], Gianni Ciolli<br />
<br />
* walbouncer: Filtering the PostgreSQL transaction log, Hans-Jürgen Schönig<br />
<br />
=== Keynotes ===<br />
<br />
* NoSQL on Acid – Maximizing Results With JSONB And PostgreSQL, Keith Alsheimer<br />
<br />
* PostgreSQL Odyssey at 88mph, Simon Riggs<br />
<br />
* [https://github.com/trustly/keynotes/raw/master/PgConf%202014%20Trustly.pdf How we use PostgreSQL at Trustly], Joel Jacobson<br />
<br />
* Closing Session, Dave Page, Magnus Hagander</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=23603PostgreSQL Conference Europe Talks 20142014-10-26T22:28:59Z<p>Fuzzycz: /* Renacimiento I */</p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
* Rendimiento: el bueno, el malo y el feo, Álvaro Herrera<br />
<br />
=== Medici III ===<br />
<br />
* Migration to PostgreSQL, Joe Conway, Michael Meskes<br />
* PostgreSQL and Java, Alvaro Hernandez<br />
<br />
=== Renacimiento I ===<br />
<br />
* Data analysis, Hans-Jürgen Schönig<br />
* [https://wiki.postgresql.org/images/d/de/NoSQL_training_-_pgconf.eu.pdf NoSQL on Acid – Maximizing Results with JSONB and PostgreSQL], Bruce Momjian, Thom Brown<br />
<br />
=== Florencia II ===<br />
<br />
* PostgreSQL Backups, Replication & Disaster Recovery, Simon Riggs<br />
<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Keynote ===<br />
<br />
* Not Only NoSQL: A Case for NoSQL + PostgreSQL in a Big Data World, Matt Asay<br />
<br />
=== Medici I ===<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)], Alexey Klyukin<br />
<br />
* What's new in PostgreSQL 9.4, Magnus Hagander<br />
<br />
* Who's the Fairest of Them All? Postgres Interface Performance, Joe Conway<br />
<br />
* [http://momjian.us/main/presentations/overview.html#scaling Postgres Scaling Opportunities], Bruce Momjian<br />
<br />
* Row Level Security, Stephen Frost<br />
<br />
* cstore_fdw, a columnar store for PostgreSQL, Ben Redman, Hadi Moshayedi<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III (Spanish track) ===<br />
<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure], Rafael Martinez Guerrero<br />
<br />
* Desmitificando la búsqueda de Postgresql, Javier ramirez<br />
<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS], Alejandro E. Brito Monedero<br />
<br />
* Características para Inteligencia de Negocios en Postgres, Álvaro Herrera<br />
<br />
* Almacenamiento de archivos en PostgreSQL: pros y contras, Martín Marqués<br />
<br />
* Domando a la bestia "replicación", Jaime Casanova<br />
<br />
=== Renacimiento I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]], Gabrielle Roth<br />
<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] ([[#http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|slideshare]]), Tomas Vondra<br />
<br />
* [[Media: Udr-pgconf.pdf|UDR - Uni Directional Replication]], Petr Jelinek<br />
<br />
* [http://www.dalibo.org/_media/opm_talk_en.pdf OPM - Open PostgreSQL Monitoring], Jean-Paul Argudo and Julien Rouhaud<br />
<br />
* Choosing the right filesystem for PostgreSQL, Devrim GÜNDÜZ<br />
<br />
* You'd better have tested backups..., Dimitri Fontaine<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* CartoDB: Empowering dynamic mapping with PostgreSQL, Alejandro Martínez<br />
<br />
* [http://michael.otacoo.com/content/materials/20140919_pgopen_logirep.pdf Understanding logical decoding and replication], Michael Paquier<br />
<br />
* [http://momjian.us/main/presentations/features.html#indexing Flexible Indexing with Postgres], Bruce Momjian<br />
<br />
* Formalising SQL in Higher-Order Logic, Gianni Ciolli, Marco Maggesi<br />
<br />
* Locks unpicked, Álvaro Herrera, Simon Riggs<br />
<br />
* Analytical PostgreSQL -- Ordered set aggregates and Grouping Sets, Atri Sharma<br />
<br />
=== Medici III ===<br />
<br />
* Open Source - A Blessing Or A Curse?, Michael Meskes<br />
<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News], Vincent Picavet<br />
<br />
* Ruling the Galaxy with PostgreSQL: Stories from the ESA Gaia Archive, Juan Gonzalez Nunez<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment], Jim Mlodgenski<br />
<br />
* How we fixed bugs and rescued data, Harald Armin Massa<br />
<br />
=== Renacimiento I ===<br />
<br />
* Loading data in PostgreSQL, Fast. Any Data., Dimitri Fontaine<br />
<br />
* Advanced Authentication, Stephen Frost<br />
<br />
* [http://thebuild.com/presentations/corruption-pgconfeu-2014.pdf Finding and Repairing Data Corruption], Christophe Pettus<br />
<br />
* Scaling fashionably: From Startup to Scale at Zalando, Valentine Gogichashvili<br />
<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool], Kaarel Moppel<br />
<br />
* Advanced Use of pg_stat_statements: Filtering, Regression Testing & more, Lukas Fittl<br />
<br />
=== Lightning Talks ===<br />
<br />
* [https://drive.google.com/file/d/0B-SFRgngatN_alhyWmZDdHRFcjQ/view?usp=sharing map()/reduce() with PostgreSQL + PL/Proxy], Ernst-Georg Schmid<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [https://github.com/Su-Shee/talks Database Unit Testing with PgTAP], Susanne Schmidt<br />
<br />
* Common difficulties for new PostgreSQL users - and what we can do about them, Craig Ringer<br />
<br />
* Hacking PostgreSQL, Stephen Frost<br />
<br />
* [https://github.com/akorotkov/talks/raw/master/pgconfeu-2014-jsquery.pdf Jsquery - the jsonb query language with GIN indexing support], Alexander Korotkov<br />
<br />
=== Medici III ===<br />
<br />
* [http://www.slideshare.net/oseemann/scaling-a-saas-backend-with-postgresql-a-case-study Scaling a SaaS backend with PostgreSQL], Oliver Seemann<br />
<br />
* [https://wiki.postgresql.org/wiki/File:RDS_EUPostgres2014_final.pptx Amazon RDS for PostgreSQL], Grant McAlister<br />
<br />
* ToroDB: a new, open-source, document-oriented, JSON database, built on Postgres, Alvaro Hernandez<br />
<br />
* Submitting a proper Postgres bug report, Jon Erdman<br />
<br />
=== Renaciemiento I ===<br />
<br />
* [http://andres.people.2ndquadrant.com/pgconf-eu-2014-10-23/bdr.pdf BDR - Asynchronous multimaster for postgres], Andres Freund<br />
<br />
* [http://thebuild.com/presentations/backups-pgconfeu-2014.pdf Be Very Afraid: Disaster Planning and Recovery], Christophe Pettus<br />
<br />
* Logical Decoding for Auditing, Gianni Ciolli<br />
<br />
* walbouncer: Filtering the PostgreSQL transaction log, Hans-Jürgen Schönig<br />
<br />
=== Keynotes ===<br />
<br />
* NoSQL on Acid – Maximizing Results With JSONB And PostgreSQL, Keith Alsheimer<br />
<br />
* PostgreSQL Odyssey at 88mph, Simon Riggs<br />
<br />
* [https://github.com/trustly/keynotes/raw/master/PgConf%202014%20Trustly.pdf How we use PostgreSQL at Trustly], Joel Jacobson<br />
<br />
* Closing Session, Dave Page, Magnus Hagander</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=23602PostgreSQL Conference Europe Talks 20142014-10-26T22:28:35Z<p>Fuzzycz: /* Renaciemiento I */</p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
* Rendimiento: el bueno, el malo y el feo, Álvaro Herrera<br />
<br />
=== Medici III ===<br />
<br />
* Migration to PostgreSQL, Joe Conway, Michael Meskes<br />
* PostgreSQL and Java, Alvaro Hernandez<br />
<br />
=== Renacimiento I ===<br />
<br />
* Data analysis, Hans-Jürgen Schönig<br />
* [https://wiki.postgresql.org/images/d/de/NoSQL_training_-_pgconf.eu.pdf NoSQL on Acid – Maximizing Results with JSONB and PostgreSQL], Bruce Momjian, Thom Brown<br />
<br />
=== Florencia II ===<br />
<br />
* PostgreSQL Backups, Replication & Disaster Recovery, Simon Riggs<br />
<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Keynote ===<br />
<br />
* Not Only NoSQL: A Case for NoSQL + PostgreSQL in a Big Data World, Matt Asay<br />
<br />
=== Medici I ===<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)], Alexey Klyukin<br />
<br />
* What's new in PostgreSQL 9.4, Magnus Hagander<br />
<br />
* Who's the Fairest of Them All? Postgres Interface Performance, Joe Conway<br />
<br />
* [http://momjian.us/main/presentations/overview.html#scaling Postgres Scaling Opportunities], Bruce Momjian<br />
<br />
* Row Level Security, Stephen Frost<br />
<br />
* cstore_fdw, a columnar store for PostgreSQL, Ben Redman, Hadi Moshayedi<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III (Spanish track) ===<br />
<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure], Rafael Martinez Guerrero<br />
<br />
* Desmitificando la búsqueda de Postgresql, Javier ramirez<br />
<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS], Alejandro E. Brito Monedero<br />
<br />
* Características para Inteligencia de Negocios en Postgres, Álvaro Herrera<br />
<br />
* Almacenamiento de archivos en PostgreSQL: pros y contras, Martín Marqués<br />
<br />
* Domando a la bestia "replicación", Jaime Casanova<br />
<br />
=== Renacimiento I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]], Gabrielle Roth<br />
<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] ([[#http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|slideshare]]), Tomas Vondra<br />
<br />
* [[Media: Udr-pgconf.pdf|UDR - Uni Directional Replication]], Petr Jelinek<br />
<br />
* [http://www.dalibo.org/_media/opm_talk_en.pdf OPM - Open PostgreSQL Monitoring], Jean-Paul Argudo and Julien Rouhaud<br />
<br />
* Choosing the right filesystem for PostgreSQL, Devrim GÜNDÜZ<br />
<br />
* You'd better have tested backups..., Dimitri Fontaine<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* CartoDB: Empowering dynamic mapping with PostgreSQL, Alejandro Martínez<br />
<br />
* [http://michael.otacoo.com/content/materials/20140919_pgopen_logirep.pdf Understanding logical decoding and replication], Michael Paquier<br />
<br />
* [http://momjian.us/main/presentations/features.html#indexing Flexible Indexing with Postgres], Bruce Momjian<br />
<br />
* Formalising SQL in Higher-Order Logic, Gianni Ciolli, Marco Maggesi<br />
<br />
* Locks unpicked, Álvaro Herrera, Simon Riggs<br />
<br />
* Analytical PostgreSQL -- Ordered set aggregates and Grouping Sets, Atri Sharma<br />
<br />
=== Medici III ===<br />
<br />
* Open Source - A Blessing Or A Curse?, Michael Meskes<br />
<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News], Vincent Picavet<br />
<br />
* Ruling the Galaxy with PostgreSQL: Stories from the ESA Gaia Archive, Juan Gonzalez Nunez<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment], Jim Mlodgenski<br />
<br />
* How we fixed bugs and rescued data, Harald Armin Massa<br />
<br />
=== Renacimiento I ===<br />
<br />
* Loading data in PostgreSQL, Fast. Any Data., Dimitri Fontaine<br />
<br />
* Advanced Authentication, Stephen Frost<br />
<br />
* Finding and Repairing Data Corruption, Christophe Pettus<br />
<br />
* Scaling fashionably: From Startup to Scale at Zalando, Valentine Gogichashvili<br />
<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool], Kaarel Moppel<br />
<br />
* Advanced Use of pg_stat_statements: Filtering, Regression Testing & more, Lukas Fittl<br />
<br />
=== Lightning Talks ===<br />
<br />
* [https://drive.google.com/file/d/0B-SFRgngatN_alhyWmZDdHRFcjQ/view?usp=sharing map()/reduce() with PostgreSQL + PL/Proxy], Ernst-Georg Schmid<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [https://github.com/Su-Shee/talks Database Unit Testing with PgTAP], Susanne Schmidt<br />
<br />
* Common difficulties for new PostgreSQL users - and what we can do about them, Craig Ringer<br />
<br />
* Hacking PostgreSQL, Stephen Frost<br />
<br />
* [https://github.com/akorotkov/talks/raw/master/pgconfeu-2014-jsquery.pdf Jsquery - the jsonb query language with GIN indexing support], Alexander Korotkov<br />
<br />
=== Medici III ===<br />
<br />
* [http://www.slideshare.net/oseemann/scaling-a-saas-backend-with-postgresql-a-case-study Scaling a SaaS backend with PostgreSQL], Oliver Seemann<br />
<br />
* [https://wiki.postgresql.org/wiki/File:RDS_EUPostgres2014_final.pptx Amazon RDS for PostgreSQL], Grant McAlister<br />
<br />
* ToroDB: a new, open-source, document-oriented, JSON database, built on Postgres, Alvaro Hernandez<br />
<br />
* Submitting a proper Postgres bug report, Jon Erdman<br />
<br />
=== Renaciemiento I ===<br />
<br />
* [http://andres.people.2ndquadrant.com/pgconf-eu-2014-10-23/bdr.pdf BDR - Asynchronous multimaster for postgres], Andres Freund<br />
<br />
* [http://thebuild.com/presentations/backups-pgconfeu-2014.pdf Be Very Afraid: Disaster Planning and Recovery], Christophe Pettus<br />
<br />
* Logical Decoding for Auditing, Gianni Ciolli<br />
<br />
* walbouncer: Filtering the PostgreSQL transaction log, Hans-Jürgen Schönig<br />
<br />
=== Keynotes ===<br />
<br />
* NoSQL on Acid – Maximizing Results With JSONB And PostgreSQL, Keith Alsheimer<br />
<br />
* PostgreSQL Odyssey at 88mph, Simon Riggs<br />
<br />
* [https://github.com/trustly/keynotes/raw/master/PgConf%202014%20Trustly.pdf How we use PostgreSQL at Trustly], Joel Jacobson<br />
<br />
* Closing Session, Dave Page, Magnus Hagander</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=23601PostgreSQL Conference Europe Talks 20142014-10-26T22:28:02Z<p>Fuzzycz: /* Keynotes */</p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
* Rendimiento: el bueno, el malo y el feo, Álvaro Herrera<br />
<br />
=== Medici III ===<br />
<br />
* Migration to PostgreSQL, Joe Conway, Michael Meskes<br />
* PostgreSQL and Java, Alvaro Hernandez<br />
<br />
=== Renacimiento I ===<br />
<br />
* Data analysis, Hans-Jürgen Schönig<br />
* [https://wiki.postgresql.org/images/d/de/NoSQL_training_-_pgconf.eu.pdf NoSQL on Acid – Maximizing Results with JSONB and PostgreSQL], Bruce Momjian, Thom Brown<br />
<br />
=== Florencia II ===<br />
<br />
* PostgreSQL Backups, Replication & Disaster Recovery, Simon Riggs<br />
<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Keynote ===<br />
<br />
* Not Only NoSQL: A Case for NoSQL + PostgreSQL in a Big Data World, Matt Asay<br />
<br />
=== Medici I ===<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)], Alexey Klyukin<br />
<br />
* What's new in PostgreSQL 9.4, Magnus Hagander<br />
<br />
* Who's the Fairest of Them All? Postgres Interface Performance, Joe Conway<br />
<br />
* [http://momjian.us/main/presentations/overview.html#scaling Postgres Scaling Opportunities], Bruce Momjian<br />
<br />
* Row Level Security, Stephen Frost<br />
<br />
* cstore_fdw, a columnar store for PostgreSQL, Ben Redman, Hadi Moshayedi<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III (Spanish track) ===<br />
<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure], Rafael Martinez Guerrero<br />
<br />
* Desmitificando la búsqueda de Postgresql, Javier ramirez<br />
<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS], Alejandro E. Brito Monedero<br />
<br />
* Características para Inteligencia de Negocios en Postgres, Álvaro Herrera<br />
<br />
* Almacenamiento de archivos en PostgreSQL: pros y contras, Martín Marqués<br />
<br />
* Domando a la bestia "replicación", Jaime Casanova<br />
<br />
=== Renacimiento I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]], Gabrielle Roth<br />
<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] ([[#http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|slideshare]]), Tomas Vondra<br />
<br />
* [[Media: Udr-pgconf.pdf|UDR - Uni Directional Replication]], Petr Jelinek<br />
<br />
* [http://www.dalibo.org/_media/opm_talk_en.pdf OPM - Open PostgreSQL Monitoring], Jean-Paul Argudo and Julien Rouhaud<br />
<br />
* Choosing the right filesystem for PostgreSQL, Devrim GÜNDÜZ<br />
<br />
* You'd better have tested backups..., Dimitri Fontaine<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* CartoDB: Empowering dynamic mapping with PostgreSQL, Alejandro Martínez<br />
<br />
* [http://michael.otacoo.com/content/materials/20140919_pgopen_logirep.pdf Understanding logical decoding and replication], Michael Paquier<br />
<br />
* [http://momjian.us/main/presentations/features.html#indexing Flexible Indexing with Postgres], Bruce Momjian<br />
<br />
* Formalising SQL in Higher-Order Logic, Gianni Ciolli, Marco Maggesi<br />
<br />
* Locks unpicked, Álvaro Herrera, Simon Riggs<br />
<br />
* Analytical PostgreSQL -- Ordered set aggregates and Grouping Sets, Atri Sharma<br />
<br />
=== Medici III ===<br />
<br />
* Open Source - A Blessing Or A Curse?, Michael Meskes<br />
<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News], Vincent Picavet<br />
<br />
* Ruling the Galaxy with PostgreSQL: Stories from the ESA Gaia Archive, Juan Gonzalez Nunez<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment], Jim Mlodgenski<br />
<br />
* How we fixed bugs and rescued data, Harald Armin Massa<br />
<br />
=== Renacimiento I ===<br />
<br />
* Loading data in PostgreSQL, Fast. Any Data., Dimitri Fontaine<br />
<br />
* Advanced Authentication, Stephen Frost<br />
<br />
* Finding and Repairing Data Corruption, Christophe Pettus<br />
<br />
* Scaling fashionably: From Startup to Scale at Zalando, Valentine Gogichashvili<br />
<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool], Kaarel Moppel<br />
<br />
* Advanced Use of pg_stat_statements: Filtering, Regression Testing & more, Lukas Fittl<br />
<br />
=== Lightning Talks ===<br />
<br />
* [https://drive.google.com/file/d/0B-SFRgngatN_alhyWmZDdHRFcjQ/view?usp=sharing map()/reduce() with PostgreSQL + PL/Proxy], Ernst-Georg Schmid<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [https://github.com/Su-Shee/talks Database Unit Testing with PgTAP], Susanne Schmidt<br />
<br />
* Common difficulties for new PostgreSQL users - and what we can do about them, Craig Ringer<br />
<br />
* Hacking PostgreSQL, Stephen Frost<br />
<br />
* [https://github.com/akorotkov/talks/raw/master/pgconfeu-2014-jsquery.pdf Jsquery - the jsonb query language with GIN indexing support], Alexander Korotkov<br />
<br />
=== Medici III ===<br />
<br />
* [http://www.slideshare.net/oseemann/scaling-a-saas-backend-with-postgresql-a-case-study Scaling a SaaS backend with PostgreSQL], Oliver Seemann<br />
<br />
* [https://wiki.postgresql.org/wiki/File:RDS_EUPostgres2014_final.pptx Amazon RDS for PostgreSQL], Grant McAlister<br />
<br />
* ToroDB: a new, open-source, document-oriented, JSON database, built on Postgres, Alvaro Hernandez<br />
<br />
* Submitting a proper Postgres bug report, Jon Erdman<br />
<br />
=== Renaciemiento I ===<br />
<br />
* [http://andres.people.2ndquadrant.com/pgconf-eu-2014-10-23/bdr.pdf BDR - Asynchronous multimaster for postgres], Andres Freund<br />
<br />
* Be Very Afraid: Disaster Planning and Recovery, Christophe Pettus<br />
<br />
* Logical Decoding for Auditing, Gianni Ciolli<br />
<br />
* walbouncer: Filtering the PostgreSQL transaction log, Hans-Jürgen Schönig<br />
<br />
=== Keynotes ===<br />
<br />
* NoSQL on Acid – Maximizing Results With JSONB And PostgreSQL, Keith Alsheimer<br />
<br />
* PostgreSQL Odyssey at 88mph, Simon Riggs<br />
<br />
* [https://github.com/trustly/keynotes/raw/master/PgConf%202014%20Trustly.pdf How we use PostgreSQL at Trustly], Joel Jacobson<br />
<br />
* Closing Session, Dave Page, Magnus Hagander</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=23600PostgreSQL Conference Europe Talks 20142014-10-26T22:27:29Z<p>Fuzzycz: </p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
* Rendimiento: el bueno, el malo y el feo, Álvaro Herrera<br />
<br />
=== Medici III ===<br />
<br />
* Migration to PostgreSQL, Joe Conway, Michael Meskes<br />
* PostgreSQL and Java, Alvaro Hernandez<br />
<br />
=== Renacimiento I ===<br />
<br />
* Data analysis, Hans-Jürgen Schönig<br />
* [https://wiki.postgresql.org/images/d/de/NoSQL_training_-_pgconf.eu.pdf NoSQL on Acid – Maximizing Results with JSONB and PostgreSQL], Bruce Momjian, Thom Brown<br />
<br />
=== Florencia II ===<br />
<br />
* PostgreSQL Backups, Replication & Disaster Recovery, Simon Riggs<br />
<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Keynote ===<br />
<br />
* Not Only NoSQL: A Case for NoSQL + PostgreSQL in a Big Data World, Matt Asay<br />
<br />
=== Medici I ===<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)], Alexey Klyukin<br />
<br />
* What's new in PostgreSQL 9.4, Magnus Hagander<br />
<br />
* Who's the Fairest of Them All? Postgres Interface Performance, Joe Conway<br />
<br />
* [http://momjian.us/main/presentations/overview.html#scaling Postgres Scaling Opportunities], Bruce Momjian<br />
<br />
* Row Level Security, Stephen Frost<br />
<br />
* cstore_fdw, a columnar store for PostgreSQL, Ben Redman, Hadi Moshayedi<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III (Spanish track) ===<br />
<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure], Rafael Martinez Guerrero<br />
<br />
* Desmitificando la búsqueda de Postgresql, Javier ramirez<br />
<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS], Alejandro E. Brito Monedero<br />
<br />
* Características para Inteligencia de Negocios en Postgres, Álvaro Herrera<br />
<br />
* Almacenamiento de archivos en PostgreSQL: pros y contras, Martín Marqués<br />
<br />
* Domando a la bestia "replicación", Jaime Casanova<br />
<br />
=== Renacimiento I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]], Gabrielle Roth<br />
<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] ([[#http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|slideshare]]), Tomas Vondra<br />
<br />
* [[Media: Udr-pgconf.pdf|UDR - Uni Directional Replication]], Petr Jelinek<br />
<br />
* [http://www.dalibo.org/_media/opm_talk_en.pdf OPM - Open PostgreSQL Monitoring], Jean-Paul Argudo and Julien Rouhaud<br />
<br />
* Choosing the right filesystem for PostgreSQL, Devrim GÜNDÜZ<br />
<br />
* You'd better have tested backups..., Dimitri Fontaine<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* CartoDB: Empowering dynamic mapping with PostgreSQL, Alejandro Martínez<br />
<br />
* [http://michael.otacoo.com/content/materials/20140919_pgopen_logirep.pdf Understanding logical decoding and replication], Michael Paquier<br />
<br />
* [http://momjian.us/main/presentations/features.html#indexing Flexible Indexing with Postgres], Bruce Momjian<br />
<br />
* Formalising SQL in Higher-Order Logic, Gianni Ciolli, Marco Maggesi<br />
<br />
* Locks unpicked, Álvaro Herrera, Simon Riggs<br />
<br />
* Analytical PostgreSQL -- Ordered set aggregates and Grouping Sets, Atri Sharma<br />
<br />
=== Medici III ===<br />
<br />
* Open Source - A Blessing Or A Curse?, Michael Meskes<br />
<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News], Vincent Picavet<br />
<br />
* Ruling the Galaxy with PostgreSQL: Stories from the ESA Gaia Archive, Juan Gonzalez Nunez<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment], Jim Mlodgenski<br />
<br />
* How we fixed bugs and rescued data, Harald Armin Massa<br />
<br />
=== Renacimiento I ===<br />
<br />
* Loading data in PostgreSQL, Fast. Any Data., Dimitri Fontaine<br />
<br />
* Advanced Authentication, Stephen Frost<br />
<br />
* Finding and Repairing Data Corruption, Christophe Pettus<br />
<br />
* Scaling fashionably: From Startup to Scale at Zalando, Valentine Gogichashvili<br />
<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool], Kaarel Moppel<br />
<br />
* Advanced Use of pg_stat_statements: Filtering, Regression Testing & more, Lukas Fittl<br />
<br />
=== Lightning Talks ===<br />
<br />
* [https://drive.google.com/file/d/0B-SFRgngatN_alhyWmZDdHRFcjQ/view?usp=sharing map()/reduce() with PostgreSQL + PL/Proxy], Ernst-Georg Schmid<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [https://github.com/Su-Shee/talks Database Unit Testing with PgTAP], Susanne Schmidt<br />
<br />
* Common difficulties for new PostgreSQL users - and what we can do about them, Craig Ringer<br />
<br />
* Hacking PostgreSQL, Stephen Frost<br />
<br />
* [https://github.com/akorotkov/talks/raw/master/pgconfeu-2014-jsquery.pdf Jsquery - the jsonb query language with GIN indexing support], Alexander Korotkov<br />
<br />
=== Medici III ===<br />
<br />
* [http://www.slideshare.net/oseemann/scaling-a-saas-backend-with-postgresql-a-case-study Scaling a SaaS backend with PostgreSQL], Oliver Seemann<br />
<br />
* [https://wiki.postgresql.org/wiki/File:RDS_EUPostgres2014_final.pptx Amazon RDS for PostgreSQL], Grant McAlister<br />
<br />
* ToroDB: a new, open-source, document-oriented, JSON database, built on Postgres, Alvaro Hernandez<br />
<br />
* Submitting a proper Postgres bug report, Jon Erdman<br />
<br />
=== Renaciemiento I ===<br />
<br />
* [http://andres.people.2ndquadrant.com/pgconf-eu-2014-10-23/bdr.pdf BDR - Asynchronous multimaster for postgres], Andres Freund<br />
<br />
* Be Very Afraid: Disaster Planning and Recovery, Christophe Pettus<br />
<br />
* Logical Decoding for Auditing, Gianni Ciolli<br />
<br />
* walbouncer: Filtering the PostgreSQL transaction log, Hans-Jürgen Schönig<br />
<br />
=== Keynotes ===<br />
<br />
* NoSQL on Acid – Maximizing Results With JSONB And PostgreSQL, Keith Alsheimer<br />
<br />
* PostgreSQL Odyssey at 88mph, Simon Riggs<br />
<br />
[https://github.com/trustly/keynotes/raw/master/PgConf%202014%20Trustly.pdf * How we use PostgreSQL at Trustly, Joel Jacobson]<br />
<br />
* Closing Session, Dave Page, Magnus Hagander</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=23505PostgreSQL Conference Europe Talks 20142014-10-23T23:33:19Z<p>Fuzzycz: /* Renacimiento I */</p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renacimiento I ===<br />
<br />
=== Florencia II ===<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]] Gabrielle Roth<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)] Alexey Klyukin<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III ===<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure] Rafael Martinez Guerrero<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS (Spanish track)] Alejandro E. Brito Monedero<br />
<br />
=== Renacimiento I ===<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] ([[#http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|slideshare]]) Tomas Vondra<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
=== Medici III ===<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News] Vincent Picavet<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment] Jim Mlodgenski<br />
<br />
=== Renacimiento I ===<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool ] Kaarel Moppel<br />
<br />
== Lightning Talks ==<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renaciemiento I ===</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=23504PostgreSQL Conference Europe Talks 20142014-10-23T23:32:53Z<p>Fuzzycz: /* Renacimiento I */</p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renacimiento I ===<br />
<br />
=== Florencia II ===<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]] Gabrielle Roth<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)] Alexey Klyukin<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III ===<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure] Rafael Martinez Guerrero<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS (Spanish track)] Alejandro E. Brito Monedero<br />
<br />
=== Renacimiento I ===<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] [[#http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|(slideshare)]] Tomas Vondra<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
=== Medici III ===<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News] Vincent Picavet<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment] Jim Mlodgenski<br />
<br />
=== Renacimiento I ===<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool ] Kaarel Moppel<br />
<br />
== Lightning Talks ==<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renaciemiento I ===</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=23503PostgreSQL Conference Europe Talks 20142014-10-23T23:32:35Z<p>Fuzzycz: /* Renacimiento I */</p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renacimiento I ===<br />
<br />
=== Florencia II ===<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]] Gabrielle Roth<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)] Alexey Klyukin<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III ===<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure] Rafael Martinez Guerrero<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS (Spanish track)] Alejandro E. Brito Monedero<br />
<br />
=== Renacimiento I ===<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] [[#http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|slideshare]] Tomas Vondra<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
=== Medici III ===<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News] Vincent Picavet<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment] Jim Mlodgenski<br />
<br />
=== Renacimiento I ===<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool ] Kaarel Moppel<br />
<br />
== Lightning Talks ==<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renaciemiento I ===</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=23502PostgreSQL Conference Europe Talks 20142014-10-23T23:31:33Z<p>Fuzzycz: /* Renacimiento I */</p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renacimiento I ===<br />
<br />
=== Florencia II ===<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]] Gabrielle Roth<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)] Alexey Klyukin<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III ===<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure] Rafael Martinez Guerrero<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS (Spanish track)] Alejandro E. Brito Monedero<br />
<br />
=== Renacimiento I ===<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] [[http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|slideshare]] Tomas Vondra<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
=== Medici III ===<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News] Vincent Picavet<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment] Jim Mlodgenski<br />
<br />
=== Renacimiento I ===<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool ] Kaarel Moppel<br />
<br />
== Lightning Talks ==<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renaciemiento I ===</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PostgreSQL_Conference_Europe_Talks_2014&diff=23501PostgreSQL Conference Europe Talks 20142014-10-23T23:31:05Z<p>Fuzzycz: /* Talks: Wednesday 22nd October, 2014 */</p>
<hr />
<div>= PostgreSQL Conference Europe 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://2014.pgconf.eu/<br />
<br />
== Trainings: Tuesday 21st October, 2014 ==<br />
<br />
=== Medici II ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renacimiento I ===<br />
<br />
=== Florencia II ===<br />
<br />
== Talks: Wednesday 22nd October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [[Media: Autovacuum_pgconfeu_gorthx.pdf|(Auto)Vacuum and You]] Gabrielle Roth<br />
<br />
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY (google presentation)] Alexey Klyukin<br />
<br />
* [https://s3.amazonaws.com/presentations.citusdata.com/cstore_fdw-pgconfeu-2014.pdf cstore_fdw, a columnar store for PostgreSQL] Ben Redman<br />
<br />
=== Medici III ===<br />
* [http://folk.uio.no/rafael/pgconfeu2014/el_guardian_del_tesoro_pgconfeu2014.pdf El guardian del tesoro / The Guardian Of The Treasure] Rafael Martinez Guerrero<br />
* [http://www.slideshare.net/ae_bm/postgres-40626330 Experiencias con PostgreSQL en AWS (Spanish track)] Alejandro E. Brito Monedero<br />
<br />
=== Renacimiento I ===<br />
* [[Media: Performance-archaeology.pdf|Performance Archaeology]] [http://www.slideshare.net/fuzzycz/performance-archaeology-40583681|slideshare] Tomas Vondra<br />
<br />
== Talks: Thursday 23 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
* [http://www.cybertec.at/wp-content/uploads/1million.pdf Joining 1 million tables], Hans-Jürgen Schönig<br />
<br />
=== Medici III ===<br />
* [https://github.com/Oslandia/presentations/raw/master/pgconf_eu_2014/postgis_latest_news_vincent_picavet.pdf PostGIS Latest News] Vincent Picavet<br />
* [http://www.slideshare.net/jim_mlodgenski/postrgesql-hadoop Leveraging Hadoop In Your PostgreSQL Environment] Jim Mlodgenski<br />
<br />
=== Renacimiento I ===<br />
* [https://docs.google.com/presentation/d/1luiaBwulBJoubwpGxrbOabXOvIgx1chG-up_8FPV5lo/edit?usp=sharing| PgObserver - a full-blown performance monitoring tool ] Kaarel Moppel<br />
<br />
== Lightning Talks ==<br />
<br />
== Talks: Friday 24 October, 2014 ==<br />
<br />
=== Medici I ===<br />
<br />
=== Medici III ===<br />
<br />
=== Renaciemiento I ===</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=File:Performance-archaeology.pdf&diff=23500File:Performance-archaeology.pdf2014-10-23T23:29:09Z<p>Fuzzycz: pgconf.eu 2014 - performance archaeology</p>
<hr />
<div>pgconf.eu 2014 - performance archaeology</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Nordic_PGDay_2014&diff=21994Nordic PGDay 20142014-03-20T20:44:35Z<p>Fuzzycz: /* Talks: Thursday, March 20th, 2014 */</p>
<hr />
<div>==Schedule==<br />
<br />
Schedule is available at the following website: http://www.postgresql.eu/events/schedule/nordicpgday2014/<br />
<br />
== Talks: Thursday, March 20th, 2014 ==<br />
<br />
* [http://thebuild.com/presentations/worst-day-nordic-2014.pdf The worst day of your life, Christophe Pettus]<br />
* 2TB of RAM ought to be enough for anybody, Renaud Bruyeron<br />
* [http://www.hagander.net/talks/postgresql94.pdf A look at the Elephants trunk - PostgreSQL 9.4, Magnus Hagander]<br />
* [https://wiki.postgresql.org/images/2/26/Useful_yet_frequently_omitted_extensions.pdf Useful yet frequently omitted extensions], Tomas Vondra<br />
* Intro to PostgreSQL Security, Stephen Frost<br />
* [http://hlinnaka.iki.fi/presentations/NordicPGDay2014-GIN.pdf Old and new tricks with GIN], Heikki Linnakangas<br />
* [http://tapoueh.org/images/confs/NordicPGDAY.pdf PostgreSQL is YeSQL!], [http://tapoueh.org/ Dimitri Fontaine]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=File:Useful_yet_frequently_omitted_extensions.pdf&diff=21993File:Useful yet frequently omitted extensions.pdf2014-03-20T20:43:20Z<p>Fuzzycz: One of the PostgreSQL advantages is extreme flexibility and extensibility. Sadly only a very small fraction of the developers has a clear overview of what extensions are available, i.e. plugins that are easy to install and provide non-traditional custo...</p>
<hr />
<div>== Summary ==<br />
One of the PostgreSQL advantages is extreme flexibility and extensibility. Sadly only a very small fraction of the developers has a clear overview of what extensions are available, i.e. plugins that are easy to install and provide non-traditional custom data types, non-traditional data types, various libraries, administrative tools, and so on. Let's look at some interesting useful extensions that you might find useful - some delivered with PostgreSQL (hstore, ltree, pgcrypto, pg_stat_statements ...), some available on sites like PGXN (semversion, pg_reorg, pg_tap ...) or GitHub.<br />
== Licensing ==<br />
{{The PostgreSQL Licence}}</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=PGDay_FOSDEM_2013&diff=18831PGDay FOSDEM 20132013-01-10T19:54:30Z<p>Fuzzycz: </p>
<hr />
<div>= PGDay FOSDEM 2013 =<br />
<br />
This is the first PgDay we hold in Belgium. FOSDEM PGDay 2013 will be held on Feb 1st in Brussels, Belgium, at the Radisson Blu Royal hotel. As an extension to the regular PostgreSQL devroom at FOSDEM, it will cover topics for PostgreSQL users, developers and contributors, and anybody else interested in PostgreSQL<br />
<br />
== Details ==<br />
<br />
* '''Date:''' Feb 01st, 2013 9am-5pm<br />
* '''Venue:''': Radisson Blu Royal Hotel<br />
* '''Coordinator:''': PostgreSQL Europe [mailto:contact@pgconf.eu contact@pgconf.eu]<br />
* '''Website:''': http://fosdem2013.pgconf.eu/<br />
<br />
== Registration ==<br />
<br />
Attendance is €50, and registration is required: http://fosdem2013.pgconf.eu/registration/ (limited seats)<br />
<br />
== Schedule ==<br />
<br />
Schedule will be published at: http://fosdem2013.pgconf.eu/schedule/<br />
<br />
== Location and Venue ==<br />
<br />
http://fosdem2013.pgconf.eu/venue/<br />
<br />
Address: <br />
<br />
http://www.radissonblu.com/royalhotel-brussels/location<br />
<br />
<br />
== Dinner ==<br />
<br />
We are organizing a dinner after the event on Friday 1st, 2013 at Hard Rock Cafe Brussels. We have limited (30) number of seats, so please add your name to this list before going there.<br />
<br />
If you are bringing someone to the event, make sure you enter your name *twice* (or more) on the list, so the attendee count matches!<br />
<br />
Attendees:<br />
<br />
# Devrim Gündüz<br />
# Devrim Gündüz +1<br />
# Magnus Hagander<br />
# Andreas Scherbaum<br />
# Andreas Scherbaum +1<br />
# Jean-Paul Argudo<br />
# Patryk Kordylewski<br />
# Patryk Kordylewski +1<br />
# Dimitri Fontaine<br />
# Julien Rouhaud<br />
# Dave Page<br />
# Marc Cousin<br />
# Stéphane Schildknecht<br />
# Stéphane Schildknecht +1<br />
# Jehan-Guillaume de Rorthais<br />
# Guillaume Lelarge<br />
# Markus Winand<br />
# Marc Balmer<br />
# Marc Balmer +1<br />
# Stefan Kaltenbrunner<br />
# Ronan Dunklau<br />
# Gilles Darold<br />
# Vik Fearing<br />
# Vik Fearing +1<br />
# Robert Ivens<br />
# Tomas Vondra<br />
<br />
[[Category:PostgreSQL Events]]</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Estimating_Distinct&diff=13195Estimating Distinct2011-03-01T23:22:43Z<p>Fuzzycz: </p>
<hr />
<div>__NOTOC__<br />
<br />
This page describes possible ways to improve estimates of number of distinct values. Originally this was a side-effect of an [http://wiki.postgresql.org/wiki/Cross_Columns_Stats effort to implement cross-column statistics] as one of the proposed approaches needs more precise distinct estimates, but as it's somehow separate effort I've created a separate page.<br />
<br />
== Sampling based estimators ==<br />
<br />
The traditional estimators in statistics are based on small sample (say 1% of the population). This works quite well except in case of distinct values, where it fails unless a very large portion of the table is sampled (see the following section).<br />
<br />
== Charikar and Chaudhuri ==<br />
<br />
In their paper (published in 2000), they stated and proved that a estimators based on sampling are a dead-end. The theorem they proved (Theorem 1) basically says that for every estimate based on a small-sample, there's a data set where the ratio error can be made arbitrarily large. The theorem is a bit more complicated (relates the size of the sample, maximal error and the probability of getting such data set), but it the end it says that you can't get a good estimator based on a small sample. And if you replace one estimator with another one, you may fix behavior for one data set, but there is another one.<br />
<br />
JOSH BERKUS: Sorry, that paper does NOT say the above. Read it again. It says that perfect sample-based estimates are impossible ... but so are perfect steam-based estimates. In general, the paper says that you can reduce the sample size required or the error rate by knowing enough to choose a sample algorithm based on the expected distribution type of the error, and that reducing the error rate is difficult without this knowledge. Also, I'll note that 2000 was hardly the end of sample estimation papers.<br />
<br />
They provide "optimal estimator" that consistently reaches the lower bound of the ratio error, but in general there are better estimators (although for some data sets they fail much harder).<br />
<br />
TOMAS VONDRA: But that's exactly the point of that theorem. They basically say "for each estimator based on a sample, we'll give you a data set where it fails with error inverse proportional to the sample size (i.e. the smaller the sample, the bigger the error)." Sure, there are estimators that perform better than the proposed "optimal estimator" for some inputs, but the beauty (and purpose) of the optimal estimator is that it's consistent for all possible data sets.<br />
<br />
== Stream based estimators ==<br />
<br />
Databases are not the only field where number of distinct values is needed - another field that needs this is data stream analysis. The proposed estimators are based on one pass through the data with incremental updates of a bitmap - the first such estimator was based on probabilistic counting, the next one on Wegman's adaptive sampling etc. In 2010 an algorithm with arbitrary precision and O(log(n)) space complexity was described - that's very promising.<br />
<br />
It's very similar to [http://en.wikipedia.org/wiki/Bloom_filter Bloom filter], but the Bloom filter needs more space and provides more information - it's designed to identify elements of the set (in this case distinct values). Which is not the case of bitmaps used in probabilistic counting etc.<br />
<br />
A very interesting approach, called Distinct sampling, was described by Gibbons in 2001. Don't be confused by the 'sampling' - it's not a random sampling, it is based on adaptive selection of a sample during one pass through the data (the principle is very similar to the Wegman's adaptive sampling). This algorithm needs much more space, but it can give estimates to question like 'how many distinct values satisfies predicate P' which is not possible with the 'simple' algorithms.<br />
<br />
So this is much more interesting, but there are a few drawbacks. First, these estimators require one pass through the data (and then incremental updates), which is completely different from the current estimators. Second, these estimators are designed for 'data streams' where there are no deletes by default. Some of the algorithms do actually describe some solution.<br />
<br />
== Papers ==<br />
<br />
This is a list of papers relevant to distinct estimation, classified into three sections. The papers are always sorted from newest to the oldest. If you know about an interesting paper not listed here, feel free to add it here.<br />
<br />
=== Sampling papers ===<br />
<br />
# '''Towards Estimation Error Guarantees for Distinct Values''' [http://ftp.cse.buffalo.edu/users/azhang/disc/disc01/cd1/out/papers/pods/towardsestimatimosur.pdf PDF]<br />
#* published: 2000<br />
#* authors: Moses Charikar, Surajit Chaudhuri, Rajeev Motwani, Vivek Narasayya<br />
#* presents a proof that with a limited sample, you really can't get a precise estimate (with limited error)<br />
#* in other words: for each estimator based on a limited sample, there's a probability distribution where the estimator fails spectacularly<br />
#* so to get a good estimate, you really need to sample most of the table (almost all of it)<br />
#* they provide an "optimal estimator" (a hybrid estimator composed of several simple estimators) in the sense that it reaches the lowest possible error (among sampling based estimators)<br />
# '''Estimating the Number of Classes in a Finite Population''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.93.8637 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.93.8637&rep=rep1&type=pdf PDF]<br />
#* published: 1996<br />
#* authors: Peter J. Haas, Lynne Stokes<br />
#* presents several sampling-based estimators, we're currently using one of them (D_uj1)<br />
# '''Sampling-Based Estimation of the Number of Distinct Values of an Attribute''' [http://www.vldb.org/conf/1995/P311.PDF PDF]<br />
#* published: 1995<br />
#* authors: Peter J. Haas, Jeffrey F. Naughtont, S. Seshadrit, Lynne Stokes<br />
#* presents several sampling-based estimators, compares them etc.<br />
#* this is a year older that the article from Hass/Stokes, so read that one instead<br />
<br />
=== Stream papers ===<br />
<br />
# '''An Optimal Algorithm for the Distinct Elements Problem''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.163.375 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.163.375&rep=rep1&type=pdf PDF]<br />
#* published: 2010 (PODS’10, June 6–11, 2010)<br />
#* authors: Daniel M. Kane, Jelani Nelson, David P. Woodruff<br />
#* basically an improved version of the "probabilistic counting" (see the paper by P. Flajolet and G. N. Martin)<br />
#* they present an algorithm with O(log(n)) bits of space and O(1) update complexity<br />
#* the precision may be improved by combining several such estimators<br />
# '''Distinct-Values Estimation over Data Streams''' [http://www.pittsburgh.intel-research.net/people/gibbons/talks-surveys/Distinct-Values-Estimation-over-Data-Streams-PBGibbons.pdf PDF]<br />
#* published: 2009<br />
#* author: Phillip B. Gibbons <br />
#* this is a quite nice summary of the possible approaches - a short paragraph about sampling-based algorithms and why this is a dead-end, a more thorough analysis of streaming based algorithms (Flajolet-Martin probabilistic counting algorithm and then another algorithm from Alon, Matias and Szegedy) and then a section about "coordinated sampling"<br />
#* there is a very nice table of various algorithms summarizing their features (if there is a sample of distinct values, if deletions are handled somehow etc.)<br />
# '''Distinct Counting with a Self-Learning Bitmap''' [http://ect.bell-labs.com/who/aychen/sbitmap4p.pdf PDF]<br />
#* published: 2009<br />
#* authors: Aiyou Chen, Jin Cao<br />
#* they describe an algorithm that performs adaptive sampling using a bitmap<br />
#* the algorithm is based on Markov chain model, but in general it seems similar to the Wegman's adaptive sampling (see the paper from 1990)<br />
# '''Distinct Sampling for Highly-Accurate Answers to Distinct Values Queries and Event Reports''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.145.550 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.145.550&rep=rep1&type=pdf PDF]<br />
#* published: 2001<br />
#* author: Phillip B. Gibbons <br />
#* although the title says "sampling" this paper is not about a traditional sampling (collecting a small random sample from a table and then computing an estimate from it), it's about collecting a sample from a stream of data (one pass through the table) and choosing a "distinct sample"<br />
#* this does not provide just an estimate on number of distinct rows, but estimate for distinct values for arbitrary predicate on the row<br />
#* seems very interesting, although it needs much more span than the other 'probabilistic counting' algoritms<br />
# '''On Adaptive Sampling''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.52.1548 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.52.1548&rep=rep1&type=pdf PDF]<br />
#* published: 1990<br />
#* authors: Philippe Flajolet<br />
#* presents an algorithm alternative to probabilistic counting, based on Wegman's Adaptive Sampling<br />
#* this algorithm is less precise than the original probabilistic counting algorithm, but is better for small files (unbiased)<br />
# '''Probabilistic Counting Algorithms for Data Base Applications''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.12.7100 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.12.7100&rep=rep1&type=pdf PDF]<br />
#* published: 1985<br />
#* authors: Philippe Flajolet, G. Nigel Martin<br />
#* this is the first paper on this topic, describes a basic algorithm and an improved "stochastic" version (PCSA)<br />
#* includes quite thorough proofs of theorems, etc.<br />
<br />
=== Related papers ===<br />
<br />
# '''Towards Estimating the Number of Distinct Value Combinations for a Set of Attributes''' [http://www.yorku.ca/xhyu/publications/cikm05.pdf PDF]<br />
#* published: 2005<br />
#* authors: Xiaohui Yu, Calisto Zuzarte, Kenneth C. Sevcik<br />
#* this paper is not about estimating number of distinct values for individual columns, but for combination of multiple columns using knowledge of their distribution (or an approximation in the form of histogram)<br />
#* the algorithm they propose is called COLSCARD<br />
#* a big disadvantage of the paper is that they assume independence of the columns, but it seems this could be solved using a multi-dimensional histogram (just replace the multiplication of distributions with the value from histogram)<br />
#* could be a way if we can't use some 'streaming' solution (in that case we could rather easily collect data not just about individual columns but about an interesting combination too)</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Cross_Columns_Stats&diff=12871Cross Columns Stats2010-12-27T14:43:43Z<p>Fuzzycz: /* A) Discrete values and inequality conditions */</p>
<hr />
<div>__NOTOC__<br />
<br />
This page is an overview of an attempt to implement cross-column statistics, i.e. an effort to enhance the optimizer so that it can perform better in case the columns of a table are not independent. You'll find examples of fail cases here, ideas on how the solution might work, links to papers on this topic, etc.<br />
<br />
Most of the information listed comes from the discussions on a mailing list (especially [http://archives.postgresql.org/pgsql-hackers/2010-12/msg00913.php this thread]), but it's quite difficult to follow the topic once it reaches some size. So from this point of view, this page is just an easily readable summary.<br />
<br />
== Possible road-map ==<br />
<br />
Simply said, there is no clear road-map, rather a general direction that may suddenly change. The current intent is to build a set of proof of concepts, attempting to build various possibilities, and then maybe a contrib module for estimating COUNT(*) results (which is very useful for pagination). And then, if everything works fine, this might be eventually used within the core.<br />
<br />
== Attribute Value Independence assumption ==<br />
<br />
The attribute value independence assumption is the root cause of the problems - it's equivalent to the [http://en.wikipedia.org/wiki/Statistical_independence statistical independence] of columns. According to this assumption, the [http://en.wikipedia.org/wiki/Joint_distribution joint distribution] is equal to multiplication of the probability distributions of individual columns.<br />
<br />
When the columns are not statistically independent, this usually leads to severe underestimate of the number of rows. And in reality, columns are almost never independent. The question is how strong the dependence actually is.<br />
<br />
Let's see a real-world example.<br />
<br />
== Example ==<br />
<br />
A typical fail case is a table with ZIP codes and city names. Those two columns are highly dependent, as a ZIP code generally determines a city.<br />
<br />
Assume there are 100 cities, each of them has 100 ZIP codes. That means there are 100 cities and 10.000 ZIP codes. When estimating a number of rows satisfying a condition <br />
<br />
<pre>WHERE zip_code = '12345' AND city = 'cityname'</pre><br />
<br />
the optimizer currently does this<br />
<br />
# estimates the selectivity of "zip_code = '12345'" (assuming uniform distribution, the selectivity is 1/10.000 = 0.01%)<br />
# estimates the selectivity of "city = 'cityname'" (assuming uniform distribution, the selectivity is 1/100 = 1%)<br />
# multiplies the selectivities and gets selectivity 0.0001%<br />
<br />
The problem is the actual selectivity is 0.01%, as the ZIP code implies the city. So the obtained estimate will be 100x underestimated. And by combining more conditions, this might lead to even worse estimates. This may be serious issue, as the planner might decide to use an index scan instead of a sequential scan in such cases. And with a complicated query, the effects are sometimes very difficult to predict.<br />
<br />
All this is due to "attribute value independence" which is basically the same as [http://en.wikipedia.org/wiki/Independence_(probability_theory) statistical independence] in probability theory.<br />
<br />
If you need a real-world sample data to play with, try [http://www.census.gov/geo/www/tiger/zip1999.html 1999 U.S. Postal Service ZIP Codes] (or directly [http://www.census.gov/geo/www/tiger/zip1999.zip ZIP]). It's not exactly fresh, but it's good enough. It's in DBF format so you'll need to use something to extract the data (e.g. [http://pgdbf.sourceforge.net PgDBF]).<br />
<br />
== Assumptions, assumptions, assumptions ... ==<br />
<br />
When collecting stats and using them to estimate the number of rows, there is always some assumption that says "if this holds, then the estimate should not be very far from the actual value." The problem is real-world data sets almost never satisfy these assumptions perfectly.<br />
<br />
One example of such assumption - attribute value independence assumption (AVI) - was already mentioned above, along with a fail case. But there are several other assumptions, some of them are used at a different place, some of them are a possible replacement for the AVI assumption. Just a very short list<br />
<br />
* '''uniform distribution''' within a histogram bin - the optimizer assumes that within a histogram bin, the values are uniformly distributed<br />
* '''uniform correlation''' - instead of independence, it's assumed that ''P(A=a|B=b)=c'' (constant), so that ''P(A=a,B=b)=P(A=a|B=b)*P(B=b)=c*P(B=b)''<br />
* '''conditional independence''' - this is a bit more complicated, see for example the paper ''Selectivity Estimation using Probabilistic Models'' [4]<br />
<br />
The idea is to replace a very strong assumption (e.g. AVI) with a much weaker one (e.g. the uniform correlation or conditional independence). Breaking a weaker assumption usually results in a much smaller error of the estimate.<br />
<br />
== Instances of the problem ==<br />
<br />
As I've explained in [http://archives.postgresql.org/pgsql-hackers/2010-12/msg01623.php this post], I think there are four very different instances of this problem. Maybe there is a 'unified theory' that handles all of them, but I'm not aware of it. So what instances are there?<br />
<br />
First, there are two quite different types of variables (columns) - numeric and discrete. And by discrete I don't mean integers, but values that serve as a label - names (city, person) are an excellent example. Discrete columns may be actually encoded as numbers, as for example ZIP codes. At first sight these types may seem equal, but that really is not the case - you can do a lot of things with numeric values that either can't be done at all with discrete values or the result does not make much sense. For example subtracting ZIP codes, computing average of city names, and so on.<br />
<br />
Second, there are two types of conditions - equality and inequality (range) conditions. These two types of conditions usually need different types of stats, so let's handle them separately.<br />
<br />
So in the end, there are four distinct instances of the problem:<br />
<br />
{| cellpadding="5" cellspacing="0" border="1"<br />
|<br />
|'''equality conditions'''<br />
|'''inequality conditions'''<br />
|-<br />
|'''discrete values'''<br />
|A<br />
|D<br />
|-<br />
|'''numeric values'''<br />
|C<br />
|B<br />
|}<br />
<br />
=== A) Discrete values and equality conditions ===<br />
<br />
One of the papers (A Bayesian Approach to Estimating The Selectivity of Conjuctive Predicates) describes a quite interesting solution to this problem - I've already posted a description on how to apply it to the ZIP code / city name problem - see [http://archives.postgresql.org/pgsql-hackers/2010-12/msg01576.php this post] and the following discussion.<br />
<br />
This basically replaces the AVI assumption with a uniform correlation assumption, which is much weaker. There are some nice features (easy extension to more than two columns, a small amount of data to keep), and some unsolved issues related to estimating number of distinct values (for individual columns and for the combination that is used in a query). The current (sampling-based) estimator has known problems, especially in case of the combination - an effort to implement better estimator is described [http://wiki.postgresql.org/wiki/Estimating_Distinct here].<br />
<br />
=== B) Numeric values and inequality conditions ===<br />
<br />
Most of the papers dealing with this problem are based on [http://en.wikipedia.org/wiki/Discretization_of_continuous_features discretization] and multi-dimensional histograms to approximate the joint distribution. So I guess my original proposal (see the first PoC) was not a complete nonsense, as it was based on this approach. Once we have a working histogram-based solution, we can work on precision and efficiency (how much space is needed to store the histogram, how long does it take to compute an estimate, etc.). According to the papers, there are two ways to do that (if you know about other solutions, let us know).<br />
<br />
First, there are several papers offering various enhanced types of multi-dimensional histograms (GenHist, SGRID, VMHIST, ...). Sure, every paper states that the histogram they described is actually the best one (most efficient, most precise, etc.) which is a bit suspicious. Anyway there are promising ways to build better multi-dimensional histograms.<br />
<br />
Second, the paper "Selectivity estimation using probabilistic models") describes a completely different solution based on [http://en.wikipedia.org/wiki/Bayesian_network Bayesian Networks]. That seems to be a really interesting alternative (and it actually it addresses join selectivity estimation too).<br />
<br />
So although the initial implementation is probably going to be inefficient and imprecise, I'm quite confident we can improve that significantly. Either by an advanced histogram or using [http://en.wikipedia.org/wiki/Bayesian_network Bayesian Networks].<br />
<br />
=== C) Numeric values and equality conditions ===<br />
<br />
I'm not sure how to handle this case. But the queries against numeric queries are range queries in most cases I guess, so maybe that's not that big deal.<br />
<br />
=== D) Discrete values and inequality conditions ===<br />
<br />
Basically, this can be handled just like numeric values after discretization, i.e. using a histogram. But just like in the previous case this is not a very frequent case. E.g. how often do you run something like this<br />
<pre>SELECT * FROM foo WHERE (zip_code BETWEEN '12899' AND '23890') AND (city_name BETWEEN 'Boston' AND 'Chicago')</pre><br />
Probably not very often.<br />
<br />
=== Combination of discrete / numeric columns ===<br />
<br />
I'm not sure how to deal with this right now. Obviously it's possible to build multi-dimensional histogram, and estimate as many queries as possible.<br />
<br />
== Proof of Concepts ==<br />
<br />
Until now, I've built two proof of concepts - the first one addresses the case B (numeric data with range conditions), the second one addresses case A (discrete data with equality conditions).<br />
<br />
=== Numeric data & range queries ===<br />
<br />
This proof of concept was described in the [http://archives.postgresql.org/pgsql-hackers/2010-12/msg00913.php initial proposal]. It's based on multi-dimensional (a quite primitive one).<br />
<br />
=== Discrete data & equality queries ===<br />
<br />
This proof of concept is thoroughly described in [http://archives.postgresql.org/pgsql-hackers/2010-12/msg01576.php this post]. It's based on the paper ''A Bayesian Approach to Estimating the Selectivity of Conjunctive Predicates'' [2].<br />
<br />
== Possible features ==<br />
<br />
This section discusses various features the solution might possibly have, what are the pros/cons of those features etc.<br />
<br />
=== Optional vs. automatic ===<br />
<br />
It's not very likely the stats will be collected automatically - see the next section.<br />
<br />
=== Collecting data for all combinations of columns ===<br />
<br />
I really don't think we should collect statistics for every combination of columns of a table. Collecting cross-column stats may consume a lot of resources (time, CPU, memory, I/O, ...), so collecting it for every combination is not very efficient. The plan is to allow a DBA to enable cross-column stats (using an ALTER TABLE, a PL/pgSQL procedure etc.) only when really needed, i.e. when these conditions are met:<br />
<br />
* the columns are dependent<br />
* the columns are used in a query together (frequently)<br />
* the current estimate is significantly imprecise, resulting in a choice of an inefficient query plan<br />
<br />
It's not very likely the stats will be collected automatically for every combination of columns.<br />
<br />
=== Collecting stats for multi-column indexes ===<br />
<br />
The only case where collecting the cross-column stats may be collected automatically is when there is a multi-column index. This usually indicates that the columns are frequently used together (which is one of the conditions), and there's a slight chance that the index may be used to build the histogram much more efficiently. But there are some counterarguments<br />
<br />
* a multi-column index does not mean the columns are dependent (producing invalid estimates)<br />
* many developers often replace multi-column index with a collection of simple indexes (and leave the database to handle it using a Bitmap Index Scan)<br />
<br />
=== Testing for independence ===<br />
<br />
There are independence tests for contingency tables (e.g. [http://mathworld.wolfram.com/Chi-SquaredTest.html Pearson's Chi-squared test]), so that it's easy to find out whether the columns are independent. If such test shows that the columns are independent, we can just throw away the cross-column stats and use the simple estimation based on attribute value independence.<br />
<br />
=== Identifying columns frequently used together ===<br />
<br />
I've noticed demands to collect data about columns used frequently together in a single WHERE condition. This might be an interesting feature (especially when the estimate significantly differs from the actual value), but it's not a part of this effort (currently).<br />
<br />
== History & Discussions ==<br />
<br />
This is just a list of thread in archives discussing cross-column statistics. This by no means a comprehensive listing (e.g. there's a lot of items in pgsql-performance archive discussing issues caused by incorrect estimates):<br />
<br />
* [http://archives.postgresql.org/pgsql-performance/2003-05/msg00049.php Hypothetical suggestions for planner, indexing improvement] - pgsql-performance, May 2003<br />
* [http://archives.postgresql.org/pgsql-hackers/2005-02/msg00208.php Cross column statistics] - pgsql-hackers, February 2006<br />
* [http://archives.postgresql.org/pgsql-hackers/2006-08/msg00463.php An Idea for planner hints] - pgsql-hackers, August 2006<br />
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01131.php Stats for multi-column indexes] - pgsql-hackers, March 2007<br />
* [http://archives.postgresql.org/pgsql-hackers/2009-06/msg01431.php Multi-Dimensional Histograms] - pgsql-hackers, June 2009<br />
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg00741.php Cross-column statistics revisited] - pgsql-hackers, October 2010<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-07/msg00529.php cross column correlation revisted] - pgsql-hackers, July 2010<br />
* [http://archives.postgresql.org/pgsql-hackers/2010-12/msg00913.php proposal: cross-column stats] - pgsql-hackers, December 2010<br />
<br />
== Interesting papers ==<br />
<br />
There are many interesting papers on selectivity estimation out there. This is a list of papers I've read recently, along with a short description. If you know about another interesting paper on this topic (selectivity estimation, especially with dependent columns), just put it here. The section is split into two - the 'recommended articles' list the really interesting articles (not obsolete, giving general into into the fields or describing a very interesting approach). The 'additional articles' is used for articles that may be interesting in the future, are obsolete, or describe a solution that is not directly applicable to PostgreSQL (e.g. involving random sampling).<br />
<br />
=== Recommended papers ===<br />
# '''The New Jersey Data Reduction Report''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.47.7751 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.47.7751&rep=rep1&type=pdf PDF]<br />
#* published in 1997, authors: Daniel Barbara, William Dumouchel, Christos Faloutsos, Peter J. Haas, Joseph M. Hellerstein, Yannis Ioannidis, H. V. Jagadish, Theodore Johnson, Raymond Ng, Viswanath Poosala, Kenneth A. Ross, Kenneth C. Sevcik<br />
#* a very thorough introduction into 'data reduction' i.e. representing data with a model<br />
#* covers about all the possibilities mentioned here (histograms, SVD, sampling) and some more (log linear models)<br />
#* does not cover probabilistic models<br />
#* anyway this is probably the best starting point if you need an intro into this topic - it's thorough, well written, covers most of the knowledge, etc.<br />
# '''A Bayesian Approach to Estimating the Selectivity of Conjunctive Predicates''' [http://subs.emis.de/LNI/Proceedings/Proceedings144/52.pdf PDF]<br />
#* published in 2009, authors: Max Heimel, Volker Markl, Keshava Murthy<br />
#* is based assuming "uniform correlation" which is a much weaker assumption compared to attribute value independence<br />
#* is easily extensible to more than two columns<br />
#* gives good estimates for highly correlated columns<br />
#* does not need sophisticated techniques as multi-dimensional histograms etc.<br />
#* seems to be a quite good solution to the "ZIP code" fail case<br />
#* there are some weak points - most serious one is the need to get good estimates of number of distinct values (individual columns and the combination used for a query)<br />
# '''Selectivity Estimation Without the Attribute Value Independence Assumption''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.105.8126 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.105.8126&rep=rep1&type=pdf PDF]<br />
#* published in 1997, authors: Viswanath Poosala, Yannis E. Ioannidis<br />
#* there's nothing revolutionary new - it just shows alternative way to build multidimensional histograms (and a completely different approach based on [http://en.wikipedia.org/wiki/Singular_value_decomposition SVD])<br />
#* the histograms are designed to be more efficient and accurate, so it might be a quite interesting improvement in the future, once we have a working (but imprecise) solution<br />
# '''Selectivity Estimation using Probabilistic Models''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.17.5550 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.17.5550&rep=rep1&type=pdf PDF]<br />
#* published in 2001, authors Lise Getoor, Ben Taskar, Daphne Koller<br />
#* exchanges the dreaded "attribute value independence" assumption for a much weaker "conditional independence" assumption, which is then used to build Bayesian Network (BN) / Probability Relational Model (PRM)<br />
#* obviously this may be used to deduce estimates for a single table as well as for joins<br />
#* I haven't studied the BN / PRM construction thoroughtly, but it seems quite tractable (and there's a list of articles that describe this)<br />
#* the main effect of the BN/PRM approach is that it significantly reduces the amount of data needed to store joint distribution (instead of storing the whole table, it stores just a few conditional probabilities)<br />
#* this may be actually built on top of a multidimensional histogram, as we need to discretize the values somehow (unless the data already is discrete, of course)<br />
# '''Selectivity estimators for multidimensional range queries over real attributes''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.122.914 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.122.914&rep=rep1&type=pdf PDF]<br />
#* published in 2005, authors: Dimitrios Gunopulos, George Kollios, Vassilis J. Tsotras, Carlotta Domeniconi<br />
#* a really nice wrap-up of problems related to cross-column statistics, and a summary of possible solutions (histograms, SVD, DCT, ...)<br />
#* summarizes problems when building histograms in higher (more than 1D) dimensions, i.e. number of cells growing exponentially (more space to store, more intersections for queries) vs. bigger (less accurate) cells.<br />
#* offers two new estimators - GENHIST and kernel estimators<br />
#* '''GENHIST''' is an alternative way to build histograms, allowing intersecting cells (contrary to usual histograms partitioning the space into non-overlapping regions)<br />
#* '''kernel estimators''' are an enhanced version of random sampling, with a quite interesting speed/accuracy and and other advantages (not based on histograms), but I guess that's not very useful to us as we're not doing any sampling<br />
<br />
=== Additional papers ===<br />
# '''Query Optimization''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.24.4154 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.24.4154&rep=rep1&type=pdf PDF]<br />
#* published in 1996, author: Yannis E. Ioannidis<br />
#* a quite nice theoretical introduction into selectivity estimation, worth reading if you know nothing about the general principles<br />
# '''Improved Histograms for Selectivity Estimation of Range Predicates''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.52.7679 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.52.7679&rep=rep1&type=pdf PDF]<br />
#* published in 1996, authors: Viswanath Poosala, Yannis E. Ioannidis, Peter J. Haas, Eugene J. Shekita<br />
#* about the same as "Selectivity Estimation Without the Attribute Value Independence Assumption" (written by two of the authors in 1997)<br />
#* does not discuss some of the alternatives (SVD for example) and contains a slightly different tests.<br />
#* there is a very interesting chapter 7 on computational techniques (spreads, quantiles, distinct values, construction costs for the histograms, required sample size etc.)<br />
# '''STHoles: A MultidimensionalWorkloadAware Histogram''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.21.1695 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.21.1695&rep=rep1&type=pdf PDF]<br />
#* published in 2001, authors: Nicolas Bruno, Surajit Chaudhuri, Luis Gravano<br />
#* another type of histogram - this case it's not build directly from the datasets, but from query results, and it's not a one-time process, the histogram is continuously improved (refined in the frequently queried regions).<br />
#* I haven't read the whole article, but although it seems quite interesting it's not very probable this would get into the core soon, and there's nothing like this (updating stats based on query results)<br />
#* so it's an interesting topic, but it's out of scope for now.<br />
# '''Summary Grids: Building Accurate Multidimensional Histograms''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.23.8475 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.23.8475&rep=rep1&type=pdf PDF]<br />
#* published in 1999, authors: Pedro Furtado, H. Madeira<br />
#* describes an alternative way to build multidimensional histograms - traditional algrithms (MHIST, PHASE) work top-down, i.e. partition the space into smaller and smaller more homogenous areas (buckets), this new algorithm (called SGRID) works bottom-up, i.e. it incrementally joins homogenous areas into larger buckets<br />
#* again, this is not quite interesting right at the beginning, maybe later when improving the solution (making it more efficient, occupy less space etc.)<br />
# '''Vmhist: Efficient Multidimensional Histograms with Improved Accuracy''' [http://eden.dei.uc.pt/~henrique/papers/vmhist.pdf PDF]<br />
#* published in 2000, authors: Pedro Furtado, Henrique Madeira<br />
#* description of another histogram, called VMHIST<br />
#* authors claim this gives better results than MHIST (see one of the other articles) and is better scalable<br />
#* the article is quite coarse, there are not many details about the algorithm and the comparison is not very thorough<br />
# '''Balancing histogram optimality and practicality for query result size estimation''' [http://reference.kfupm.edu.sa/content/b/a/balancing_histogram_optimality_and_pract_46453.pdf PDF]<br />
#* published in 1995, authors: Yannis E. Ioannidis, Viswanath Poosala<br />
#* seems to be a quite old article, and is mostly obsolete (i.e. the following articles from Ioannidis are much more interesting as more advanced histograms are presented)<br />
#* contains some basic definitions, lemmas etc.<br />
# '''Fast and Effective Histogram Construction''' [http://felix-halim.net/research/histogram/index.php WWW] [http://felix-halim.net/research/histogram/KM0563-halim.pdf PDF]<br />
#* published in 2009, authors: Felix Halim, Panagiotis Karras, Roland H. C. Yap<br />
#* another article proposing a new way to build histograms, comparing to older histograms, etc.<br />
# '''HASE: A Hybrid Approach to Selectivity Estimation for Conjunctive Predicates''' [http://www.yorku.ca/xhyu/publications/edbt06.pdf PDF]<br />
#* published in 2006, authors: Xiaohui Yu1, Nick Koudas1, Calisto Zuzarte<br />
#* attempts to combine estimates from synopsis (pregenerated info - e.g. histogram) and random sampling (performed when the query is planned)<br />
#* currently these two approaches are used separately, and they attempt to combine, eliminate drawbacks and get the best parts of both<br />
#* right now this is rather useless for us, as we're not using random sampling at all (maybe in the future this might be an interesting improvement)<br />
# '''Histogram-Based Approximation of Set-Valued Query Answers''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.58.5501 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.58.5501&rep=rep1&type=pdf PDF]<br />
#* published in 1999, authors: Yannis E. Ioannidis, Viswanath Poosala<br />
#* not exactly about estimation, rather about approximating results of queries returning sets of rows<br />
#* contains some interesting info, but not exactly relevant to estimation</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Estimating_Distinct&diff=12870Estimating Distinct2010-12-27T14:38:33Z<p>Fuzzycz: </p>
<hr />
<div>__NOTOC__<br />
<br />
This page describes possible ways to improve estimates of number of distinct values. Originally this was a side-effect of an [http://wiki.postgresql.org/wiki/Cross_Columns_Stats effort to implement cross-column statistics] as one of the proposed approaches needs more precise distinct estimates, but as it's somehow separate effort I've created a separate page.<br />
<br />
== Sampling based estimators ==<br />
<br />
The traditional estimators in statistics are based on small sample (say 1% of the population). This works quite well except in case of distinct values, where it fails unless a very large portion of the table is sampled (see the following section).<br />
<br />
== Charikar and Chaudhuri ==<br />
<br />
In their paper (published in 2000), they stated and proved that a estimators based on sampling are a dead-end. The theorem they proved (Theorem 1) basically says that for every estimate based on a small-sample, there's a data set where the ratio error can be made arbitrarily large. The theorem is a bit more complicated (relates the size of the sample, maximal error and the probability of getting such data set), but it the end it says that you can't get a good estimator based on a small sample. And if you replace one estimator with another one, you may fix behavior for one data set, but there is another one.<br />
<br />
They provide "optimal estimator" that consistently reaches the lower bound of the ratio error, but in general there are better estimators (although for some data sets they fail much harder).<br />
<br />
== Stream based estimators ==<br />
<br />
Databases are not the only field where number of distinct values is needed - another field that needs this is data stream analysis. The proposed estimators are based on one pass through the data with incremental updates of a bitmap - the first such estimator was based on probabilistic counting, the next one on Wegman's adaptive sampling etc. In 2010 an algorithm with arbitrary precision and O(log(n)) space complexity was described - that's very promising.<br />
<br />
It's very similar to [http://en.wikipedia.org/wiki/Bloom_filter Bloom filter], but the Bloom filter needs more space and provides more information - it's designed to identify elements of the set (in this case distinct values). Which is not the case of bitmaps used in probabilistic counting etc.<br />
<br />
A very interesting approach, called Distinct sampling, was described by Gibbons in 2001. Don't be confused by the 'sampling' - it's not a random sampling, it is based on adaptive selection of a sample during one pass through the data (the principle is very similar to the Wegman's adaptive sampling). This algorithm needs much more space, but it can give estimates to question like 'how many distinct values satisfies predicate P' which is not possible with the 'simple' algorithms.<br />
<br />
So this is much more interesting, but there are a few drawbacks. First, these estimators require one pass through the data (and then incremental updates), which is completely different from the current estimators. Second, these estimators are designed for 'data streams' where there are no deletes by default. Some of the algorithms do actually describe some solution.<br />
<br />
== Papers ==<br />
<br />
This is a list of papers relevant to distinct estimation, classified into three sections. The papers are always sorted from newest to the oldest. If you know about an interesting paper not listed here, feel free to add it here.<br />
<br />
=== Sampling papers ===<br />
<br />
# '''Towards Estimation Error Guarantees for Distinct Values''' [http://ftp.cse.buffalo.edu/users/azhang/disc/disc01/cd1/out/papers/pods/towardsestimatimosur.pdf PDF]<br />
#* published: 2000<br />
#* authors: Moses Charikar, Surajit Chaudhuri, Rajeev Motwani, Vivek Narasayya<br />
#* presents a proof that with a limited sample, you really can't get a precise estimate (with limited error)<br />
#* in other words: for each estimator based on a limited sample, there's a probability distribution where the estimator fails spectacularly<br />
#* so to get a good estimate, you really need to sample most of the table (almost all of it)<br />
#* they provide an "optimal estimator" (a hybrid estimator composed of several simple estimators) in the sense that it reaches the lowest possible error (among sampling based estimators)<br />
# '''Estimating the Number of Classes in a Finite Population''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.93.8637 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.93.8637&rep=rep1&type=pdf PDF]<br />
#* published: 1996<br />
#* authors: Peter J. Haas, Lynne Stokes<br />
#* presents several sampling-based estimators, we're currently using one of them (D_uj1)<br />
# '''Sampling-Based Estimation of the Number of Distinct Values of an Attribute''' [http://www.vldb.org/conf/1995/P311.PDF PDF]<br />
#* published: 1995<br />
#* authors: Peter J. Haas, Jeffrey F. Naughtont, S. Seshadrit, Lynne Stokes<br />
#* presents several sampling-based estimators, compares them etc.<br />
#* this is a year older that the article from Hass/Stokes, so read that one instead<br />
<br />
=== Stream papers ===<br />
<br />
# '''An Optimal Algorithm for the Distinct Elements Problem''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.163.375 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.163.375&rep=rep1&type=pdf PDF]<br />
#* published: 2010 (PODS’10, June 6–11, 2010)<br />
#* authors: Daniel M. Kane, Jelani Nelson, David P. Woodruff<br />
#* basically an improved version of the "probabilistic counting" (see the paper by P. Flajolet and G. N. Martin)<br />
#* they present an algorithm with O(log(n)) bits of space and O(1) update complexity<br />
#* the precision may be improved by combining several such estimators<br />
# '''Distinct-Values Estimation over Data Streams''' [http://www.pittsburgh.intel-research.net/people/gibbons/talks-surveys/Distinct-Values-Estimation-over-Data-Streams-PBGibbons.pdf PDF]<br />
#* published: 2009<br />
#* author: Phillip B. Gibbons <br />
#* this is a quite nice summary of the possible approaches - a short paragraph about sampling-based algorithms and why this is a dead-end, a more thorough analysis of streaming based algorithms (Flajolet-Martin probabilistic counting algorithm and then another algorithm from Alon, Matias and Szegedy) and then a section about "coordinated sampling"<br />
#* there is a very nice table of various algorithms summarizing their features (if there is a sample of distinct values, if deletions are handled somehow etc.)<br />
# '''Distinct Counting with a Self-Learning Bitmap''' [http://ect.bell-labs.com/who/aychen/sbitmap4p.pdf PDF]<br />
#* published: 2009<br />
#* authors: Aiyou Chen, Jin Cao<br />
#* they describe an algorithm that performs adaptive sampling using a bitmap<br />
#* the algorithm is based on Markov chain model, but in general it seems similar to the Wegman's adaptive sampling (see the paper from 1990)<br />
# '''Distinct Sampling for Highly-Accurate Answers to Distinct Values Queries and Event Reports''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.145.550 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.145.550&rep=rep1&type=pdf PDF]<br />
#* published: 2001<br />
#* author: Phillip B. Gibbons <br />
#* although the title says "sampling" this paper is not about a traditional sampling (collecting a small random sample from a table and then computing an estimate from it), it's about collecting a sample from a stream of data (one pass through the table) and choosing a "distinct sample"<br />
#* this does not provide just an estimate on number of distinct rows, but estimate for distinct values for arbitrary predicate on the row<br />
#* seems very interesting, although it needs much more span than the other 'probabilistic counting' algoritms<br />
# '''On Adaptive Sampling''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.52.1548 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.52.1548&rep=rep1&type=pdf PDF]<br />
#* published: 1990<br />
#* authors: Philippe Flajolet<br />
#* presents an algorithm alternative to probabilistic counting, based on Wegman's Adaptive Sampling<br />
#* this algorithm is less precise than the original probabilistic counting algorithm, but is better for small files (unbiased)<br />
# '''Probabilistic Counting Algorithms for Data Base Applications''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.12.7100 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.12.7100&rep=rep1&type=pdf PDF]<br />
#* published: 1985<br />
#* authors: Philippe Flajolet, G. Nigel Martin<br />
#* this is the first paper on this topic, describes a basic algorithm and an improved "stochastic" version (PCSA)<br />
#* includes quite thorough proofs of theorems, etc.<br />
<br />
=== Related papers ===<br />
<br />
# '''Towards Estimating the Number of Distinct Value Combinations for a Set of Attributes''' [http://www.yorku.ca/xhyu/publications/cikm05.pdf PDF]<br />
#* published: 2005<br />
#* authors: Xiaohui Yu, Calisto Zuzarte, Kenneth C. Sevcik<br />
#* this paper is not about estimating number of distinct values for individual columns, but for combination of multiple columns using knowledge of their distribution (or an approximation in the form of histogram)<br />
#* the algorithm they propose is called COLSCARD<br />
#* a big disadvantage of the paper is that they assume independence of the columns, but it seems this could be solved using a multi-dimensional histogram (just replace the multiplication of distributions with the value from histogram)<br />
#* could be a way if we can't use some 'streaming' solution (in that case we could rather easily collect data not just about individual columns but about an interesting combination too)</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Estimating_Distinct&diff=12869Estimating Distinct2010-12-27T14:35:29Z<p>Fuzzycz: </p>
<hr />
<div>__NOTOC__<br />
== Sampling based estimators ==<br />
<br />
The traditional estimators in statistics are based on small sample (say 1% of the population). This works quite well except in case of distinct values, where it fails unless a very large portion of the table is sampled (see the following section).<br />
<br />
== Charikar and Chaudhuri ==<br />
<br />
In their paper (published in 2000), they stated and proved that a estimators based on sampling are a dead-end. The theorem they proved (Theorem 1) basically says that for every estimate based on a small-sample, there's a data set where the ratio error can be made arbitrarily large. The theorem is a bit more complicated (relates the size of the sample, maximal error and the probability of getting such data set), but it the end it says that you can't get a good estimator based on a small sample. And if you replace one estimator with another one, you may fix behavior for one data set, but there is another one.<br />
<br />
They provide "optimal estimator" that consistently reaches the lower bound of the ratio error, but in general there are better estimators (although for some data sets they fail much harder).<br />
<br />
== Stream based estimators ==<br />
<br />
Databases are not the only field where number of distinct values is needed - another field that needs this is data stream analysis. The proposed estimators are based on one pass through the data with incremental updates of a bitmap - the first such estimator was based on probabilistic counting, the next one on Wegman's adaptive sampling etc. In 2010 an algorithm with arbitrary precision and O(log(n)) space complexity was described - that's very promising.<br />
<br />
It's very similar to [http://en.wikipedia.org/wiki/Bloom_filter Bloom filter], but the Bloom filter needs more space and provides more information - it's designed to identify elements of the set (in this case distinct values). Which is not the case of bitmaps used in probabilistic counting etc.<br />
<br />
A very interesting approach, called Distinct sampling, was described by Gibbons in 2001. Don't be confused by the 'sampling' - it's not a random sampling, it is based on adaptive selection of a sample during one pass through the data (the principle is very similar to the Wegman's adaptive sampling). This algorithm needs much more space, but it can give estimates to question like 'how many distinct values satisfies predicate P' which is not possible with the 'simple' algorithms.<br />
<br />
So this is much more interesting, but there are a few drawbacks. First, these estimators require one pass through the data (and then incremental updates), which is completely different from the current estimators. Second, these estimators are designed for 'data streams' where there are no deletes by default. Some of the algorithms do actually describe some solution.<br />
<br />
== Papers ==<br />
<br />
This is a list of papers relevant to distinct estimation, classified into three sections. The papers are always sorted from newest to the oldest. If you know about an interesting paper not listed here, feel free to add it here.<br />
<br />
=== Sampling papers ===<br />
<br />
# '''Towards Estimation Error Guarantees for Distinct Values''' [http://ftp.cse.buffalo.edu/users/azhang/disc/disc01/cd1/out/papers/pods/towardsestimatimosur.pdf PDF]<br />
#* published: 2000<br />
#* authors: Moses Charikar, Surajit Chaudhuri, Rajeev Motwani, Vivek Narasayya<br />
#* presents a proof that with a limited sample, you really can't get a precise estimate (with limited error)<br />
#* in other words: for each estimator based on a limited sample, there's a probability distribution where the estimator fails spectacularly<br />
#* so to get a good estimate, you really need to sample most of the table (almost all of it)<br />
#* they provide an "optimal estimator" (a hybrid estimator composed of several simple estimators) in the sense that it reaches the lowest possible error (among sampling based estimators)<br />
# '''Estimating the Number of Classes in a Finite Population''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.93.8637 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.93.8637&rep=rep1&type=pdf PDF]<br />
#* published: 1996<br />
#* authors: Peter J. Haas, Lynne Stokes<br />
#* presents several sampling-based estimators, we're currently using one of them (D_uj1)<br />
# '''Sampling-Based Estimation of the Number of Distinct Values of an Attribute''' [http://www.vldb.org/conf/1995/P311.PDF PDF]<br />
#* published: 1995<br />
#* authors: Peter J. Haas, Jeffrey F. Naughtont, S. Seshadrit, Lynne Stokes<br />
#* presents several sampling-based estimators, compares them etc.<br />
#* this is a year older that the article from Hass/Stokes, so read that one instead<br />
<br />
=== Stream papers ===<br />
<br />
# '''An Optimal Algorithm for the Distinct Elements Problem''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.163.375 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.163.375&rep=rep1&type=pdf PDF]<br />
#* published: 2010 (PODS’10, June 6–11, 2010)<br />
#* authors: Daniel M. Kane, Jelani Nelson, David P. Woodruff<br />
#* basically an improved version of the "probabilistic counting" (see the paper by P. Flajolet and G. N. Martin)<br />
#* they present an algorithm with O(log(n)) bits of space and O(1) update complexity<br />
#* the precision may be improved by combining several such estimators<br />
# '''Distinct-Values Estimation over Data Streams''' [http://www.pittsburgh.intel-research.net/people/gibbons/talks-surveys/Distinct-Values-Estimation-over-Data-Streams-PBGibbons.pdf PDF]<br />
#* published: 2009<br />
#* author: Phillip B. Gibbons <br />
#* this is a quite nice summary of the possible approaches - a short paragraph about sampling-based algorithms and why this is a dead-end, a more thorough analysis of streaming based algorithms (Flajolet-Martin probabilistic counting algorithm and then another algorithm from Alon, Matias and Szegedy) and then a section about "coordinated sampling"<br />
#* there is a very nice table of various algorithms summarizing their features (if there is a sample of distinct values, if deletions are handled somehow etc.)<br />
# '''Distinct Counting with a Self-Learning Bitmap''' [http://ect.bell-labs.com/who/aychen/sbitmap4p.pdf PDF]<br />
#* published: 2009<br />
#* authors: Aiyou Chen, Jin Cao<br />
#* they describe an algorithm that performs adaptive sampling using a bitmap<br />
#* the algorithm is based on Markov chain model, but in general it seems similar to the Wegman's adaptive sampling (see the paper from 1990)<br />
# '''Distinct Sampling for Highly-Accurate Answers to Distinct Values Queries and Event Reports''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.145.550 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.145.550&rep=rep1&type=pdf PDF]<br />
#* published: 2001<br />
#* author: Phillip B. Gibbons <br />
#* although the title says "sampling" this paper is not about a traditional sampling (collecting a small random sample from a table and then computing an estimate from it), it's about collecting a sample from a stream of data (one pass through the table) and choosing a "distinct sample"<br />
#* this does not provide just an estimate on number of distinct rows, but estimate for distinct values for arbitrary predicate on the row<br />
#* seems very interesting, although it needs much more span than the other 'probabilistic counting' algoritms<br />
# '''On Adaptive Sampling''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.52.1548 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.52.1548&rep=rep1&type=pdf PDF]<br />
#* published: 1990<br />
#* authors: Philippe Flajolet<br />
#* presents an algorithm alternative to probabilistic counting, based on Wegman's Adaptive Sampling<br />
#* this algorithm is less precise than the original probabilistic counting algorithm, but is better for small files (unbiased)<br />
# '''Probabilistic Counting Algorithms for Data Base Applications''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.12.7100 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.12.7100&rep=rep1&type=pdf PDF]<br />
#* published: 1985<br />
#* authors: Philippe Flajolet, G. Nigel Martin<br />
#* this is the first paper on this topic, describes a basic algorithm and an improved "stochastic" version (PCSA)<br />
#* includes quite thorough proofs of theorems, etc.<br />
<br />
=== Related papers ===<br />
<br />
# '''Towards Estimating the Number of Distinct Value Combinations for a Set of Attributes''' [http://www.yorku.ca/xhyu/publications/cikm05.pdf PDF]<br />
#* published: 2005<br />
#* authors: Xiaohui Yu, Calisto Zuzarte, Kenneth C. Sevcik<br />
#* this paper is not about estimating number of distinct values for individual columns, but for combination of multiple columns using knowledge of their distribution (or an approximation in the form of histogram)<br />
#* the algorithm they propose is called COLSCARD<br />
#* a big disadvantage of the paper is that they assume independence of the columns, but it seems this could be solved using a multi-dimensional histogram (just replace the multiplication of distributions with the value from histogram)<br />
#* could be a way if we can't use some 'streaming' solution (in that case we could rather easily collect data not just about individual columns but about an interesting combination too)</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Estimating_Distinct&diff=12868Estimating Distinct2010-12-27T03:03:50Z<p>Fuzzycz: /* Sampling */</p>
<hr />
<div>== Sampling ==<br />
<br />
# '''Towards Estimation Error Guarantees for Distinct Values''' [http://ftp.cse.buffalo.edu/users/azhang/disc/disc01/cd1/out/papers/pods/towardsestimatimosur.pdf PDF]<br />
#* published: 2000<br />
#* authors: Moses Charikar, Surajit Chaudhuri, Rajeev Motwani, Vivek Narasayya<br />
#* presents a proof that with a limited sample, you really can't get a precise estimate (with limited error)<br />
#* in other words: for each estimator based on a limited sample, there's a probability distribution where the estimator fails spectacularly<br />
#* so to get a good estimate, you really need to sample most of the table (almost all of it)<br />
#* they provide an "optimal estimator" (a hybrid estimator composed of several simple estimators) in the sense that it reaches the lowest possible error (among sampling based estimators)<br />
# '''Estimating the Number of Classes in a Finite Population''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.93.8637 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.93.8637&rep=rep1&type=pdf PDF]<br />
#* published: 1996<br />
#* authors: Peter J. Haas, Lynne Stokes<br />
#* presents several sampling-based estimators, we're currently using one of them (D_uj1)<br />
# '''Sampling-Based Estimation of the Number of Distinct Values of an Attribute''' [http://www.vldb.org/conf/1995/P311.PDF PDF]<br />
#* published: 1995<br />
#* authors: Peter J. Haas, Jeffrey F. Naughtont, S. Seshadrit, Lynne Stokes<br />
#* presents several sampling-based estimators, compares them etc.<br />
#* this is a year older that the article from Hass/Stokes, so read that one instead<br />
<br />
== Stream ==<br />
<br />
# '''An Optimal Algorithm for the Distinct Elements Problem''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.163.375 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.163.375&rep=rep1&type=pdf PDF]<br />
#* published: 2010 (PODS’10, June 6–11, 2010)<br />
#* authors: Daniel M. Kane, Jelani Nelson, David P. Woodruff<br />
#* basically an improved version of the "probabilistic counting" (see the paper by P. Flajolet and G. N. Martin)<br />
#* they present an algorithm with O(log(n)) bits of space and O(1) update complexity<br />
#* the precision may be improved by combining several such estimators<br />
# '''Distinct-Values Estimation over Data Streams''' [http://www.pittsburgh.intel-research.net/people/gibbons/talks-surveys/Distinct-Values-Estimation-over-Data-Streams-PBGibbons.pdf PDF]<br />
#* published: 2009<br />
#* author: Phillip B. Gibbons <br />
#* this is a quite nice summary of the possible approaches - a short paragraph about sampling-based algorithms and why this is a dead-end, a more thorough analysis of streaming based algorithms (Flajolet-Martin probabilistic counting algorithm and then another algorithm from Alon, Matias and Szegedy) and then a section about "coordinated sampling"<br />
#* there is a very nice table of various algorithms summarizing their features (if there is a sample of distinct values, if deletions are handled somehow etc.)<br />
# '''Distinct Counting with a Self-Learning Bitmap''' [http://ect.bell-labs.com/who/aychen/sbitmap4p.pdf PDF]<br />
#* published: 2009<br />
#* authors: Aiyou Chen, Jin Cao<br />
#* they describe an algorithm that performs adaptive sampling using a bitmap<br />
#* the algorithm is based on Markov chain model, but in general it seems similar to the Wegman's adaptive sampling (see the paper from 1990)<br />
# '''Distinct Sampling for Highly-Accurate Answers to Distinct Values Queries and Event Reports''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.145.550 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.145.550&rep=rep1&type=pdf PDF]<br />
#* published: 2001<br />
#* author: Phillip B. Gibbons <br />
#* although the title says "sampling" this paper is not about a traditional sampling (collecting a small random sample from a table and then computing an estimate from it), it's about collecting a sample from a stream of data (one pass through the table) and choosing a "distinct sample"<br />
#* this does not provide just an estimate on number of distinct rows, but estimate for distinct values for arbitrary predicate on the row<br />
#* seems very interesting, although it needs much more span than the other 'probabilistic counting' algoritms<br />
# '''On Adaptive Sampling''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.52.1548 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.52.1548&rep=rep1&type=pdf PDF]<br />
#* published: 1990<br />
#* authors: Philippe Flajolet<br />
#* presents an algorithm alternative to probabilistic counting, based on Wegman's Adaptive Sampling<br />
#* this algorithm is less precise than the original probabilistic counting algorithm, but is better for small files (unbiased)<br />
# '''Probabilistic Counting Algorithms for Data Base Applications''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.12.7100 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.12.7100&rep=rep1&type=pdf PDF]<br />
#* published: 1985<br />
#* authors: Philippe Flajolet, G. Nigel Martin<br />
#* this is the first paper on this topic, describes a basic algorithm and an improved "stochastic" version (PCSA)<br />
#* includes quite thorough proofs of theorems, etc.<br />
<br />
== Related ==<br />
<br />
# '''Towards Estimating the Number of Distinct Value Combinations for a Set of Attributes''' [http://www.yorku.ca/xhyu/publications/cikm05.pdf PDF]<br />
#* published: 2005<br />
#* authors: Xiaohui Yu, Calisto Zuzarte, Kenneth C. Sevcik<br />
#* this paper is not about estimating number of distinct values for individual columns, but for combination of multiple columns using knowledge of their distribution (or an approximation in the form of histogram)<br />
#* the algorithm they propose is called COLSCARD<br />
#* a big disadvantage of the paper is that they assume independence of the columns, but it seems this could be solved using a multi-dimensional histogram (just replace the multiplication of distributions with the value from histogram)<br />
#* could be a way if we can't use some 'streaming' solution (in that case we could rather easily collect data not just about individual columns but about an interesting combination too)</div>Fuzzyczhttps://wiki.postgresql.org/index.php?title=Estimating_Distinct&diff=12867Estimating Distinct2010-12-27T03:00:49Z<p>Fuzzycz: New page: == Sampling == # '''Towards Estimation Error Guarantees for Distinct Values''' [http://ftp.cse.buffalo.edu/users/azhang/disc/disc01/cd1/out/papers/pods/towardsestimatimosur.pdf PDF] #* pu...</p>
<hr />
<div>== Sampling ==<br />
<br />
# '''Towards Estimation Error Guarantees for Distinct Values''' [http://ftp.cse.buffalo.edu/users/azhang/disc/disc01/cd1/out/papers/pods/towardsestimatimosur.pdf PDF]<br />
#* published: 2000<br />
#* authors: Moses Charikar, Surajit Chaudhuri, Rajeev Motwani, Vivek Narasayya<br />
#* presents a proof that with a limited sample, you really can't get a precise estimate (with limited error)<br />
#* in other words: for each estimator based on a limited sample, there's a probabilistic distribution where the estimator fails spectacularly<br />
#* so to get a good estimate, you really need to sample most of the table (almost all of it)<br />
#* they provide an "optimal estimator" (a hybrid estimator composed of several simple estimators) in the sense that it reaches the lowest possible error (among sampling based estimators)<br />
# '''Estimating the Number of Classes in a Finite Population''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.93.8637 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.93.8637&rep=rep1&type=pdf PDF]<br />
#* published: 1996<br />
#* authors: Peter J. Haas, Lynne Stokes<br />
#* presents several sampling-based estimators, we're currently using one of them (D_uj1)<br />
# '''Sampling-Based Estimation of the Number of Distinct Values of an Attribute''' [http://www.vldb.org/conf/1995/P311.PDF PDF]<br />
#* published: 1995<br />
#* authors: Peter J. Haas, Jeffrey F. Naughtont, S. Seshadrit, Lynne Stokes<br />
#* presents several sampling-based estimators, compares them etc.<br />
#* this is a year older that the article from Hass/Stokes, so read that one instead<br />
<br />
== Stream ==<br />
<br />
# '''An Optimal Algorithm for the Distinct Elements Problem''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.163.375 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.163.375&rep=rep1&type=pdf PDF]<br />
#* published: 2010 (PODS’10, June 6–11, 2010)<br />
#* authors: Daniel M. Kane, Jelani Nelson, David P. Woodruff<br />
#* basically an improved version of the "probabilistic counting" (see the paper by P. Flajolet and G. N. Martin)<br />
#* they present an algorithm with O(log(n)) bits of space and O(1) update complexity<br />
#* the precision may be improved by combining several such estimators<br />
# '''Distinct-Values Estimation over Data Streams''' [http://www.pittsburgh.intel-research.net/people/gibbons/talks-surveys/Distinct-Values-Estimation-over-Data-Streams-PBGibbons.pdf PDF]<br />
#* published: 2009<br />
#* author: Phillip B. Gibbons <br />
#* this is a quite nice summary of the possible approaches - a short paragraph about sampling-based algorithms and why this is a dead-end, a more thorough analysis of streaming based algorithms (Flajolet-Martin probabilistic counting algorithm and then another algorithm from Alon, Matias and Szegedy) and then a section about "coordinated sampling"<br />
#* there is a very nice table of various algorithms summarizing their features (if there is a sample of distinct values, if deletions are handled somehow etc.)<br />
# '''Distinct Counting with a Self-Learning Bitmap''' [http://ect.bell-labs.com/who/aychen/sbitmap4p.pdf PDF]<br />
#* published: 2009<br />
#* authors: Aiyou Chen, Jin Cao<br />
#* they describe an algorithm that performs adaptive sampling using a bitmap<br />
#* the algorithm is based on Markov chain model, but in general it seems similar to the Wegman's adaptive sampling (see the paper from 1990)<br />
# '''Distinct Sampling for Highly-Accurate Answers to Distinct Values Queries and Event Reports''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.145.550 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.145.550&rep=rep1&type=pdf PDF]<br />
#* published: 2001<br />
#* author: Phillip B. Gibbons <br />
#* although the title says "sampling" this paper is not about a traditional sampling (collecting a small random sample from a table and then computing an estimate from it), it's about collecting a sample from a stream of data (one pass through the table) and choosing a "distinct sample"<br />
#* this does not provide just an estimate on number of distinct rows, but estimate for distinct values for arbitrary predicate on the row<br />
#* seems very interesting, although it needs much more span than the other 'probabilistic counting' algoritms<br />
# '''On Adaptive Sampling''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.52.1548 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.52.1548&rep=rep1&type=pdf PDF]<br />
#* published: 1990<br />
#* authors: Philippe Flajolet<br />
#* presents an algorithm alternative to probabilistic counting, based on Wegman's Adaptive Sampling<br />
#* this algorithm is less precise than the original probabilistic counting algorithm, but is better for small files (unbiased)<br />
# '''Probabilistic Counting Algorithms for Data Base Applications''' [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.12.7100 citeseerx] [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.12.7100&rep=rep1&type=pdf PDF]<br />
#* published: 1985<br />
#* authors: Philippe Flajolet, G. Nigel Martin<br />
#* this is the first paper on this topic, describes a basic algorithm and an improved "stochastic" version (PCSA)<br />
#* includes quite thorough proofs of theorems, etc.<br />
<br />
== Related ==<br />
<br />
# '''Towards Estimating the Number of Distinct Value Combinations for a Set of Attributes''' [http://www.yorku.ca/xhyu/publications/cikm05.pdf PDF]<br />
#* published: 2005<br />
#* authors: Xiaohui Yu, Calisto Zuzarte, Kenneth C. Sevcik<br />
#* this paper is not about estimating number of distinct values for individual columns, but for combination of multiple columns using knowledge of their distribution (or an approximation in the form of histogram)<br />
#* the algorithm they propose is called COLSCARD<br />
#* a big disadvantage of the paper is that they assume independence of the columns, but it seems this could be solved using a multi-dimensional histogram (just replace the multiplication of distributions with the value from histogram)<br />
#* could be a way if we can't use some 'streaming' solution (in that case we could rather easily collect data not just about individual columns but about an interesting combination too)</div>Fuzzycz