pgsql-hackers  

Messages by Thread

• • Re: Horribly slow pg_upgrade performance with many Large Objects Nathan Bossart
  • Re: Horribly slow pg_upgrade performance with many Large Objects Hannu Krosing
  • Re: Horribly slow pg_upgrade performance with many Large Objects Hannu Krosing
  • Re: Horribly slow pg_upgrade performance with many Large Objects Tom Lane
  • Re: Horribly slow pg_upgrade performance with many Large Objects Tom Lane
  • Re: Horribly slow pg_upgrade performance with many Large Objects Nathan Bossart
  • Re: Horribly slow pg_upgrade performance with many Large Objects Tom Lane
  • Re: Horribly slow pg_upgrade performance with many Large Objects Nathan Bossart
  • Re: Horribly slow pg_upgrade performance with many Large Objects Hannu Krosing
• Move tests of contrib/spi/ out of the core regression tests Tom Lane
  • Re: Move tests of contrib/spi/ out of the core regression tests Heikki Linnakangas
  • Re: Move tests of contrib/spi/ out of the core regression tests wenhui qiu
  • Re: Move tests of contrib/spi/ out of the core regression tests Andrew Dunstan
  • Re: Move tests of contrib/spi/ out of the core regression tests Tom Lane
  • Re: Move tests of contrib/spi/ out of the core regression tests Heikki Linnakangas
  • Re: Move tests of contrib/spi/ out of the core regression tests Tom Lane
• Re: Parameter NOT NULL to CREATE DOMAIN not the same as CHECK (VALUE IS NOT NULL) Bruce Momjian
• Can we use Statistics Import and Export feature to perforamance testing? Ryohei Takahashi (Fujitsu)
  • Re: Can we use Statistics Import and Export feature to perforamance testing? David Rowley
  • RE: Can we use Statistics Import and Export feature to perforamance testing? Ryohei Takahashi (Fujitsu)
  • Re: Can we use Statistics Import and Export feature to perforamance testing? Corey Huinker
  • Re: Can we use Statistics Import and Export feature to perforamance testing? David Rowley
  • Re: Can we use Statistics Import and Export feature to perforamance testing? Corey Huinker
  • Re: Can we use Statistics Import and Export feature to perforamance testing? Corey Huinker
• prevent 006_transfer_modes.pl from leaving files behind Nathan Bossart
  • Re: prevent 006_transfer_modes.pl from leaving files behind Michael Paquier
  • Re: prevent 006_transfer_modes.pl from leaving files behind Andrew Dunstan
  • Re: prevent 006_transfer_modes.pl from leaving files behind Tom Lane
  • Re: prevent 006_transfer_modes.pl from leaving files behind Andrew Dunstan
  • Re: prevent 006_transfer_modes.pl from leaving files behind Nathan Bossart
• [Question: linux pipes ( ... | gzip | cat ... ) in tests failing] Re: [PATCH] Adding pg_dump flag for parallel export to pipes Hannu Krosing
• Adding pg_dump flag for parallel export to pipes Nitin Motiani
  • Re: Adding pg_dump flag for parallel export to pipes Hannu Krosing
  • Re: Adding pg_dump flag for parallel export to pipes Hannu Krosing
  • Re: Adding pg_dump flag for parallel export to pipes Thomas Munro
  • Re: Adding pg_dump flag for parallel export to pipes Nitin Motiani
• Re: ci: Allow running mingw tests by default via environment variable Nazir Bilal Yavuz
  • Re: ci: Allow running mingw tests by default via environment variable Andres Freund
  • Re: ci: Allow running mingw tests by default via environment variable Thomas Munro
  • Re: ci: Allow running mingw tests by default via environment variable Nathan Bossart
  • Re: ci: Allow running mingw tests by default via environment variable Andres Freund
  • Re: ci: Allow running mingw tests by default via environment variable Nathan Bossart
• as per commit 643a1a61985bef2590496, move create/open dir code to function using switch case of pg_backup_directory.c file also Mahendra Singh Thalor
  • Re: as per commit 643a1a61985bef2590496, move create/open dir code to function using switch case of pg_backup_directory.c file also Andrew Dunstan
  • Re: as per commit 643a1a61985bef2590496, move create/open dir code to function using switch case of pg_backup_directory.c file also Mahendra Singh Thalor
  • Re: as per commit 643a1a61985bef2590496, move create/open dir code to function using switch case of pg_backup_directory.c file also Andrew Dunstan
  • Re: as per commit 643a1a61985bef2590496, move create/open dir code to function using switch case of pg_backup_directory.c file also Mahendra Singh Thalor
  • Re: as per commit 643a1a61985bef2590496, move create/open dir code to function using switch case of pg_backup_directory.c file also Álvaro Herrera
• Re: BUG #18815: Logical replication worker Segmentation fault Amit Kapila
  • RE: BUG #18815: Logical replication worker Segmentation fault Zhijie Hou (Fujitsu)
  • Re: BUG #18815: Logical replication worker Segmentation fault Amit Kapila
  • RE: BUG #18815: Logical replication worker Segmentation fault Zhijie Hou (Fujitsu)
  • Re: BUG #18815: Logical replication worker Segmentation fault Amit Kapila
• An incorrect check in get_memoize_path Richard Guo
  • Re: An incorrect check in get_memoize_path wenhui qiu
  • Re: An incorrect check in get_memoize_path Andrei Lepikhov
  • Re: An incorrect check in get_memoize_path Richard Guo
  • Re: An incorrect check in get_memoize_path Andrei Lepikhov
  • Re: An incorrect check in get_memoize_path Richard Guo
  • Re: An incorrect check in get_memoize_path Andrei Lepikhov
  • Re: An incorrect check in get_memoize_path wenhui qiu
  • Re: An incorrect check in get_memoize_path Richard Guo
• Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate Melanie Plageman
  • Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate Alexander Korotkov
  • Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate David Rowley
  • Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate Melanie Plageman
  • Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate Tom Lane
  • Re: pgsql: Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate Alexander Korotkov
• Patch for migration of the pg_commit_ts directory ls7777
• Make prep_status() message translatable Kyotaro Horiguchi
  • Re: Make prep_status() message translatable Fujii Masao
  • Re: Make prep_status() message translatable Fujii Masao
  • Re: Make prep_status() message translatable Fujii Masao
• Unquoted file name in an error message Kyotaro Horiguchi
  • Re: Unquoted file name in an error message Álvaro Herrera
  • Re: Unquoted file name in an error message Andrew Dunstan
• Correct mismatched verb in a message Kyotaro Horiguchi
  • Re: Correct mismatched verb in a message Michael Paquier
• Re: History doc page clarification on naming Daniel Gustafsson
  • Re: History doc page clarification on naming Dave Page
• BAS_BULKREAD vs read stream Andres Freund
  • Re: BAS_BULKREAD vs read stream Melanie Plageman
  • Re: BAS_BULKREAD vs read stream Andres Freund
  • Re: BAS_BULKREAD vs read stream Andres Freund
  • Re: BAS_BULKREAD vs read stream Thomas Munro
  • Re: BAS_BULKREAD vs read stream Andres Freund
  • Re: BAS_BULKREAD vs read stream Jakub Wartak
• Re: datfrozenxid > relfrozenxid w/ crash before XLOG_HEAP_INPLACE Noah Misch
  • Re: datfrozenxid > relfrozenxid w/ crash before XLOG_HEAP_INPLACE Noah Misch
• [PATCH] clarify palloc comment on quote_literal_cstr Steve Chavez
  • Re: [PATCH] clarify palloc comment on quote_literal_cstr Michael Paquier
  • Re: [PATCH] clarify palloc comment on quote_literal_cstr Ashutosh Bapat
  • Re: [PATCH] clarify palloc comment on quote_literal_cstr Steve Chavez
  • Re: [PATCH] clarify palloc comment on quote_literal_cstr Ashutosh Bapat
  • Re: [PATCH] clarify palloc comment on quote_literal_cstr Michael Paquier
  • Re: [PATCH] clarify palloc comment on quote_literal_cstr Ashutosh Bapat
  • Re: [PATCH] clarify palloc comment on quote_literal_cstr Tom Lane
  • Re: [PATCH] clarify palloc comment on quote_literal_cstr Michael Paquier
• FmgrInfo allocation patterns (and PL handling as staged programming) Chapman Flack
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Tom Lane
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Tom Lane
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Chapman Flack
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Chapman Flack
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Tom Lane
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Chapman Flack
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Tom Lane
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Chapman Flack
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Tom Lane
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Chapman Flack
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Tom Lane
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Chapman Flack
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Pavel Stehule
  • Re: FmgrInfo allocation patterns (and PL handling as staged programming) Tom Lane
  • transforms [was Re: FmgrInfo allocation patterns (and PL handling as staged programming)] Chapman Flack
  • Re: transforms [was Re: FmgrInfo allocation patterns (and PL handling as staged programming)] Tom Lane
  • Re: transforms [was Re: FmgrInfo allocation patterns (and PL handling as staged programming)] Chapman Flack
  • Re: transforms Chapman Flack
  • Re: transforms Tom Lane
  • Re: transforms Tom Lane
  • Re: transforms Chapman Flack
  • Re: transforms Tom Lane
  • Re: transforms Chapman Flack
  • Re: transforms Chapman Flack
• Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM Jingtang Zhang
  • Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM Daniil Davydov
• Re: [PATCH] New predefined role pg_manage_extensions Tom Lane
  • Re: [PATCH] New predefined role pg_manage_extensions Laurenz Albe
• Re: CREATE OR REPLACE MATERIALIZED VIEW Tom Lane
• Re: pull-up subquery if JOIN-ON contains refs to upper-query Alena Rybakina
  • Re: pull-up subquery if JOIN-ON contains refs to upper-query Ilia Evdokimov
• Remove redundant if-else in EXPLAIN by using ExplainPropertyText Ilia Evdokimov
• Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits Bertrand Drouvot
  • Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits Bertrand Drouvot
  • Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits vignesh C
  • Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits Bertrand Drouvot
  • Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits vignesh C
  • Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits Bertrand Drouvot
  • Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits vignesh C
  • Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits Michael Paquier
  • Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits Bertrand Drouvot
  • Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits Michael Paquier
• Re: Add mention in docs about locking all partitions for generic plans David Rowley
  • Re: Add mention in docs about locking all partitions for generic plans David Rowley
  • Re: Add mention in docs about locking all partitions for generic plans David Rowley
• Re: Using read_stream in index vacuum Melanie Plageman
  • Re: Using read_stream in index vacuum Melanie Plageman
  • Re: Using read_stream in index vacuum Melanie Plageman
• [PATCH] Add a new pattern for zero-based months for Date/Time Formatting Vincent Moreau
• Re: Vacuum statistics Alena Rybakina
  • Re: Vacuum statistics Andrei Lepikhov
• Re: Fix infinite loop from setting scram_iterations to INT_MAX Richard Guo
  • Re: Fix infinite loop from setting scram_iterations to INT_MAX Michael Paquier
• Hashed IN only applied to first encountered IN David Geier
  • Re: Hashed IN only applied to first encountered IN David Rowley
  • Re: Hashed IN only applied to first encountered IN David Rowley
  • Re: Hashed IN only applied to first encountered IN David Geier
• Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Noah Misch
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Michael Paquier
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Tom Lane
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Noah Misch
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Michael Paquier
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Noah Misch
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Noah Misch
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Tom Lane
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Michael Paquier
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Noah Misch
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Noah Misch
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Andres Freund
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Noah Misch
  • Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Michael Paquier
• ICU warnings during make installcheck and text_extensions test Oleg Tselebrovskiy
• Re: Conflict detection for multiple_unique_conflicts in logical replication Nisha Moond
  • RE: Conflict detection for multiple_unique_conflicts in logical replication Zhijie Hou (Fujitsu)
  • Re: Conflict detection for multiple_unique_conflicts in logical replication Nisha Moond
  • Re: Conflict detection for multiple_unique_conflicts in logical replication Peter Smith
  • Re: Conflict detection for multiple_unique_conflicts in logical replication Amit Kapila
• Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Ni Ku
  • Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Ashutosh Bapat
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Thomas Munro
  • Re: Changing shared_buffers without restart Thomas Munro
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Thomas Munro
  • Re: Changing shared_buffers without restart Andres Freund
  • Re: Changing shared_buffers without restart Ni Ku
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Konstantin Knizhnik
  • Re: Changing shared_buffers without restart Dmitry Dolgov
  • Re: Changing shared_buffers without restart Konstantin Knizhnik

• Earlier messages
• Later messages