pgsql-hackers  

Messages by Thread

• • Re: Statistics Import and Export Jeff Davis
  • Re: Statistics Import and Export Hari Krishna Sunder
  • Re: Statistics Import and Export Nathan Bossart
  • Re: Statistics Import and Export Hari Krishna Sunder
  • Re: Statistics Import and Export Hari Krishna Sunder
  • Re: Statistics Import and Export Michael Paquier
  • Re: Statistics Import and Export Nathan Bossart
  • Re: Statistics Import and Export Hari Krishna Sunder
  • Re: Statistics Import and Export Nathan Bossart
  • Re: Statistics Import and Export Hari Krishna Sunder
  • Re: Statistics Import and Export Nathan Bossart
  • Re: Statistics Import and Export Hari Krishna Sunder
  • Re: Statistics Import and Export Jeff Davis
  • Re: Statistics Import and Export Nathan Bossart
  • Re: Statistics Import and Export Corey Huinker
  • Re: Statistics Import and Export Jeff Davis
  • Re: Statistics Import and Export Nathan Bossart
  • Re: Statistics Import and Export Hari Krishna Sunder
• Re: Accessing an invalid pointer in BufferManagerRelation structure Stepan Neretin
• Re: Inval reliability, especially for inplace updates Noah Misch
• Suggestion to add --continue-client-on-abort option to pgbench ikedarintarof
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Stepan Neretin
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Matthias van de Meent
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Stepan Neretin
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Rintaro.Ikeda
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Dilip Kumar
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Srinath Reddy Sadipiralla
  • Re: Suggestion to add --continue-client-on-abort option to pgbench ikedarintarof
  • Re: Suggestion to add --continue-client-on-abort option to pgbench ikedarintarof
  • RE: Suggestion to add --continue-client-on-abort option to pgbench Hayato Kuroda (Fujitsu)
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Rintaro Ikeda
  • RE: Suggestion to add --continue-client-on-abort option to pgbench Hayato Kuroda (Fujitsu)
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Yugo Nagata
  • RE: Suggestion to add --continue-client-on-abort option to pgbench Hayato Kuroda (Fujitsu)
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Yugo Nagata
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Yugo Nagata
• is there any query that can cover these statements in join_is_legal()? g l
• Re: [PATCH] New predefined role pg_manage_extensions John H
• Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Robert Haas
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Florents Tselai
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Florents Tselai
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Robert Haas
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Tom Lane
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Robert Haas
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Florents Tselai
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Peter Eisentraut
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Robert Haas
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Florents Tselai
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Tom Lane
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Florents Tselai
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Florents Tselai
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
• Re: SQL:2011 application time Robert Haas
  • Re: SQL:2011 application time Paul A Jungwirth
  • Re: SQL:2011 application time Peter Eisentraut
  • Re: SQL:2011 application time Paul A Jungwirth
  • Re: SQL:2011 application time Peter Eisentraut
  • Re: SQL:2011 application time Tom Lane
• Fix incorrect order of params in comment Daniel Gustafsson
  • Re: Fix incorrect order of params in comment Michael Paquier
  • Re: Fix incorrect order of params in comment Daniel Gustafsson
• Re: Useless LEFT JOIN breaks MIN/MAX optimization Robert Haas
  • Re: Useless LEFT JOIN breaks MIN/MAX optimization Alena Rybakina
  • Re: Useless LEFT JOIN breaks MIN/MAX optimization Tom Lane
  • Re: Useless LEFT JOIN breaks MIN/MAX optimization Alena Rybakina
• Re: Vacuum statistics Alena Rybakina
  • Re: Vacuum statistics Amit Kapila
  • Re: Vacuum statistics Alena Rybakina
  • Re: Vacuum statistics Amit Kapila
  • Re: Vacuum statistics Alexander Korotkov
  • Re: Vacuum statistics Alena Rybakina
• Re: Restrict publishing of partitioned table with a foreign table as partition Shlok Kyal
  • Re: Restrict publishing of partitioned table with a foreign table as partition Álvaro Herrera
  • Re: Restrict publishing of partitioned table with a foreign table as partition Amit Kapila
  • Re: Restrict publishing of partitioned table with a foreign table as partition Shlok Kyal
  • Re: Restrict publishing of partitioned table with a foreign table as partition Ajin Cherian
  • Re: Restrict publishing of partitioned table with a foreign table as partition Shlok Kyal
• Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Andrey Borodin
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Thom Brown
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
• strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Aleksander Alekseev
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Aleksander Alekseev
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Andres Freund
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Andres Freund
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Alexander Lakhin
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Mihail Nikalayeu
  • Re: strange perf regression with data checksums Peter Geoghegan
• Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
  • Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
  • Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
  • Re: [PATCH] avoid double scanning in function byteain Aleksander Alekseev
  • Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
  • Re: [PATCH] avoid double scanning in function byteain Peter Eisentraut
• Re: Logical Replication of sequences shveta malik
  • Re: Logical Replication of sequences Peter Smith
  • Re: Logical Replication of sequences Nisha Moond
  • Re: Logical Replication of sequences shveta malik
  • Re: Logical Replication of sequences Peter Smith
  • Re: Logical Replication of sequences shveta malik
  • Re: Logical Replication of sequences Nisha Moond
  • Re: Logical Replication of sequences shveta malik
  • Re: Logical Replication of sequences Amit Kapila
  • Re: Logical Replication of sequences Nisha Moond
  • Re: Logical Replication of sequences Ajin Cherian
  • Re: Logical Replication of sequences vignesh C
  • Re: Logical Replication of sequences Nisha Moond
  • Re: Logical Replication of sequences Nisha Moond
  • Re: Logical Replication of sequences vignesh C
• Re: Assert failure in base_yyparse Richard Guo
  • Re: Assert failure in base_yyparse Alvaro Herrera
  • Re: Assert failure in base_yyparse Richard Guo
  • Re: Assert failure in base_yyparse Alvaro Herrera
  • Re: Assert failure in base_yyparse Richard Guo
• Re: Issues with 2PC at recovery: CLOG lookups and GlobalTransactionData Michael Paquier
  • Re: Issues with 2PC at recovery: CLOG lookups and GlobalTransactionData Michael Paquier
  • Re: Issues with 2PC at recovery: CLOG lookups and GlobalTransactionData Noah Misch
  • Re: Issues with 2PC at recovery: CLOG lookups and GlobalTransactionData Michael Paquier
  • Re: Issues with 2PC at recovery: CLOG lookups and GlobalTransactionData Noah Misch
• Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Yasir
  • Re: Why our Valgrind reports suck Andres Freund
  • Re: Why our Valgrind reports suck Andres Freund
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Álvaro Herrera
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Yasir
  • Re: Why our Valgrind reports suck Andres Freund
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Andres Freund
  • Re: Why our Valgrind reports suck Peter Geoghegan
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Yasir
• Re: Support for runtime parameters in injection points, for AIO tests Michael Paquier
  • Re: Support for runtime parameters in injection points, for AIO tests Andres Freund
  • Re: Support for runtime parameters in injection points, for AIO tests Michael Paquier
  • Re: Support for runtime parameters in injection points, for AIO tests Michael Paquier
  • Re: Support for runtime parameters in injection points, for AIO tests Michael Paquier
• Re: pgsql: Make cancel request keys longer Heikki Linnakangas
  • Re: pgsql: Make cancel request keys longer Jacob Champion
  • Re: pgsql: Make cancel request keys longer Heikki Linnakangas
  • Re: pgsql: Make cancel request keys longer Jacob Champion
• Fix PQport to never return NULL if the connection is valid Daniele Varrazzo
  • Re: Fix PQport to never return NULL if the connection is valid Daniele Varrazzo
  • Re: Fix PQport to never return NULL if the connection is valid Daniele Varrazzo

• Earlier messages
• Later messages