pgsql-hackers  

Messages by Thread

• • Re: PostgreSQL 19 Beta 4 release announcement draft Lukas Fittl
  • Re: PostgreSQL 19 Beta 4 release announcement draft Jonathan S. Katz
  • Re: PostgreSQL 19 Beta 4 release announcement draft Lukas Fittl
  • Re: PostgreSQL 19 Beta 4 release announcement draft Jonathan S. Katz
• Re: [PATCH v1] [BUG #19507] Prevent constraint name conflicts in partition trees spanning multiple schemas Manu
• Proposal: expose heavyweight lock wait start time in pg_stat_activity Alex Shapalov
  • Re: Proposal: expose heavyweight lock wait start time in pg_stat_activity Sami Imseih
  • Re: Proposal: expose heavyweight lock wait start time in pg_stat_activity shihao zhong
  • Re: Proposal: expose heavyweight lock wait start time in pg_stat_activity Alex Shapalov
  • Re: Proposal: expose heavyweight lock wait start time in pg_stat_activity shihao zhong
• Re: Validate user-supplied c_args in meson builds Tristan Partin
  • Re: Validate user-supplied c_args in meson builds Bertrand Drouvot
• Re: meson: avoid PATH bloat from NLS .mo targets in tmp_install test setup Tristan Partin
  • Re: meson: avoid PATH bloat from NLS .mo targets in tmp_install test setup Andrew Dunstan
  • Re: meson: avoid PATH bloat from NLS .mo targets in tmp_install test setup Tristan Partin
• Adding a range check on the sequence index from the publisher. Masahiko Sawada
  • Re: Adding a range check on the sequence index from the publisher. Amit Kapila
  • Re: Adding a range check on the sequence index from the publisher. Masahiko Sawada
  • Re: Adding a range check on the sequence index from the publisher. Chao Li
  • Re: Adding a range check on the sequence index from the publisher. Masahiko Sawada
  • Re: Adding a range check on the sequence index from the publisher. Chao Li
  • Re: Adding a range check on the sequence index from the publisher. Masahiko Sawada
  • Re: Adding a range check on the sequence index from the publisher. Chao Li
  • Re: Adding a range check on the sequence index from the publisher. Masahiko Sawada
  • Re: Adding a range check on the sequence index from the publisher. Chao Li
  • Re: Adding a range check on the sequence index from the publisher. Masahiko Sawada
• Re: Teach pg_upgrade to deal with invalid databases Nathan Bossart
  • Re: Teach pg_upgrade to deal with invalid databases Robert Treat
  • Re: Teach pg_upgrade to deal with invalid databases Andres Freund
  • Re: Teach pg_upgrade to deal with invalid databases Bharath Rupireddy
  • Re: Teach pg_upgrade to deal with invalid databases Nathan Bossart
  • Re: Teach pg_upgrade to deal with invalid databases Euler Taveira
  • Re: Teach pg_upgrade to deal with invalid databases Bharath Rupireddy
  • Re: Teach pg_upgrade to deal with invalid databases Bharath Rupireddy
  • Re: Teach pg_upgrade to deal with invalid databases Nathan Bossart
  • Re: Teach pg_upgrade to deal with invalid databases Bharath Rupireddy
  • Re: Teach pg_upgrade to deal with invalid databases Robert Treat
• Fix a wal_debug crash with the new shmem allocation API Bharath Rupireddy
  • Re: Fix a wal_debug crash with the new shmem allocation API Heikki Linnakangas
  • Re: Fix a wal_debug crash with the new shmem allocation API Ashutosh Bapat
  • Re: Fix a wal_debug crash with the new shmem allocation API Bharath Rupireddy
  • Re: Fix a wal_debug crash with the new shmem allocation API Heikki Linnakangas
• Re: Direct TOAST v2, faster, smaller and no migration needed Andres Freund
  • Re: Direct TOAST v2, faster, smaller and no migration needed Hannu Krosing
  • Re: Direct TOAST v2, faster, smaller and no migration needed Tomas Vondra
  • Re: Direct TOAST v2, faster, smaller and no migration needed shihao zhong
  • Re: Direct TOAST v2, faster, smaller and no migration needed Hannu Krosing
  • Re: Direct TOAST v2, faster, smaller and no migration needed Matthias van de Meent
  • Re: Direct TOAST v2, faster, smaller and no migration needed Michael Paquier
  • Re: Direct TOAST v2, faster, smaller and no migration needed Hannu Krosing
  • Re: Direct TOAST v2, faster, smaller and no migration needed Hannu Krosing
  • Re: Direct TOAST v2, faster, smaller and no migration needed Hannu Krosing
  • Re: Direct TOAST v2, faster, smaller and no migration needed Matthias van de Meent
  • Re: Direct TOAST v2, faster, smaller and no migration needed Hannu Krosing
• pg_verifybackup / pg_combinebackup: missing readdir() error check in directory scan Daria Lepikhova
• [PATCH] Halve peak memory allocation for toast_flatten_tuple Pavel Borisov
• [PATCH] unrecognized win32 error 448 (ERROR_UNTRUSTED_MOUNT_POINT) breaks tablespaces on Win11 26200 Greg Burd
  • Re: [PATCH] unrecognized win32 error 448 (ERROR_UNTRUSTED_MOUNT_POINT) breaks tablespaces on Win11 26200 Bryan Green
  • Re: [PATCH] unrecognized win32 error 448 (ERROR_UNTRUSTED_MOUNT_POINT) breaks tablespaces on Win11 26200 Greg Burd
• Re: Reduce cleanup lock contention on standby replay Melanie Plageman
• Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring Andres Freund
  • Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring Michael Paquier
  • Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring Sami Imseih
  • Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring Michael Paquier
  • Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring Melanie Plageman
  • Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring Nathan Bossart
  • Catversion bumps during beta (was Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring) Heikki Linnakangas
  • Re: Catversion bumps during beta (was Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring) Tom Lane
  • Re: Catversion bumps during beta (was Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring) Heikki Linnakangas
  • Re: Catversion bumps during beta (was Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring) Noah Misch
  • Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring Andrey Borodin
• Re: Correct some doc items due to the REPACK Álvaro Herrera
  • Re: Correct some doc items due to the REPACK Marcos Pegoraro
• Re: Write skew observed under serializable isolation Aleksander Alekseev
  • Re: Write skew observed under serializable isolation Andrey Borodin
  • Re: Write skew observed under serializable isolation Aleksander Alekseev
  • Re: Write skew observed under serializable isolation Andres Freund
  • Re: Write skew observed under serializable isolation Aleksander Alekseev
  • Re: Write skew observed under serializable isolation Zsolt Parragi
  • Re: Write skew observed under serializable isolation Aleksander Alekseev
  • Re: Write skew observed under serializable isolation Zsolt Parragi
  • Re: Write skew observed under serializable isolation Aleksander Alekseev
• pg_resetwal with replication slot (17.11) Rıdvan Korkmaz
  • Re: pg_resetwal with replication slot (17.11) Rıdvan Korkmaz
  • Re: pg_resetwal with replication slot (17.11) Chao Li
  • Re: pg_resetwal with replication slot (17.11) Chao Li
• [PATCH] set_byte() with a count argument Sehrope Sarkuni
  • Re: [PATCH] set_byte() with a count argument Matthias van de Meent
  • Re: [PATCH] set_byte() with a count argument Sehrope Sarkuni
  • Re: [PATCH] set_byte() with a count argument Matthias van de Meent
  • Re: [PATCH] set_byte() with a count argument Sehrope Sarkuni
• [PATCH] Honor LC_NUMERIC environment variable on Windows Andrew Bille
• WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Sami Imseih
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bertrand Drouvot
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Alexandre Felipe
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bertrand Drouvot
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bertrand Drouvot
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bharath Rupireddy
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Bertrand Drouvot
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Michael Paquier
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Chao Li
  • Re: WAL segment file descriptor leak on read errors can PANIC the server Chao Li
• Re: Redesign per-backend statistics Bertrand Drouvot
  • Re: Redesign per-backend statistics Andres Freund
  • Re: Redesign per-backend statistics Michael Paquier
  • Re: Redesign per-backend statistics Bertrand Drouvot
  • Re: Redesign per-backend statistics Bertrand Drouvot
• Re: Dropping a composite attribute causes data integrity violations Manuel Reyes Bravo
• [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby Naga Appani
  • Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby Heikki Linnakangas
  • Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby Michael Paquier
  • Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby Heikki Linnakangas
  • Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby Naga Appani
  • Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby Michael Paquier
  • Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby Michael Paquier
  • Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby Naga Appani
• Re: ERROR: failed to find conversion function from unknown to text Manuel Reyes Bravo
  • Re: ERROR: failed to find conversion function from unknown to text jian he
  • Re: ERROR: failed to find conversion function from unknown to text Manu
• Assert failure in get_baserel_parampathinfo with lateral UNION ALL Richard Guo
  • Re: Assert failure in get_baserel_parampathinfo with lateral UNION ALL wenhui qiu
  • Re: Assert failure in get_baserel_parampathinfo with lateral UNION ALL Richard Guo
  • Re: Assert failure in get_baserel_parampathinfo with lateral UNION ALL Richard Guo
• psql: avoid over-reading unterminated prompt escapes Chao Li
  • Re: psql: avoid over-reading unterminated prompt escapes Kirill Reshke
  • Re: psql: avoid over-reading unterminated prompt escapes Chao Li
• Video about non-volatile memory technology Bruce Momjian
• [PATCH] Assertion in pg_get_shmem_pagesize() in single-user mode Ayush Tiwari
  • Re: [PATCH] Assertion in pg_get_shmem_pagesize() in single-user mode Heikki Linnakangas
• Re: [Patch] Add WHERE clause support to REFRESH MATERIALIZED VIEW Adam Brusselback
• Re: Serverside SNI support in libpq Noah Misch
  • Re: Serverside SNI support in libpq Daniel Gustafsson
  • Re: Serverside SNI support in libpq Daniel Gustafsson
  • Re: Serverside SNI support in libpq Zsolt Parragi
  • Re: Serverside SNI support in libpq Daniel Gustafsson
  • Re: Serverside SNI support in libpq Zsolt Parragi
  • Re: Serverside SNI support in libpq Jacob Champion
  • Re: Serverside SNI support in libpq Daniel Gustafsson
  • Re: Serverside SNI support in libpq Rui Zhao
  • Re: Serverside SNI support in libpq Daniel Gustafsson
  • Re: Serverside SNI support in libpq Rui Zhao
  • Re: Serverside SNI support in libpq Daniel Gustafsson
  • Re: Serverside SNI support in libpq Jacob Champion
• Re: COMMENTS are not being copied in CREATE TABLE LIKE Alex Liapychev
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Tomas Vondra
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Jim Jones
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Alex Liapychev
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Alex Liapychev
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Jim Jones
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Tomas Vondra
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Tom Lane
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Jim Jones
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Alex Liapychev
  • Re: COMMENTS are not being copied in CREATE TABLE LIKE Jim Jones
• Re: [PATCH] Combine qual-based and NOT NULL proofs when reducing outer joins Ziming Zhang
• [PATCH] Use bounded GIN pending-list cleanup in parallel autovacuum Jingtang Zhang
  • Re: [PATCH] Use bounded GIN pending-list cleanup in parallel autovacuum Andrey Borodin
  • Re: [PATCH] Use bounded GIN pending-list cleanup in parallel autovacuum Jingtang Zhang
  • Re: [PATCH] Use bounded GIN pending-list cleanup in parallel autovacuum Yuhang Qiu
  • Re: [PATCH] Use bounded GIN pending-list cleanup in parallel autovacuum Masahiko Sawada
  • Re: [PATCH] Use bounded GIN pending-list cleanup in parallel autovacuum Jingtang Zhang
  • Re: [PATCH] Use bounded GIN pending-list cleanup in parallel autovacuum Masahiko Sawada
• ERROR: SubPlan found with no parent plan Richard Guo
• Re: Add a Nix flake Wolfgang Walther
  • Re: Add a Nix flake Álvaro Herrera
• Intermittent Assert("plan->magic == _SPI_PLAN_MAGIC") in 027_stream_regress Trakshan Mishra
• Re: Add a hook for handling logical decoding messages on subscribers. Bharath Rupireddy
  • Re: Add a hook for handling logical decoding messages on subscribers. Amit Kapila
  • Re: Add a hook for handling logical decoding messages on subscribers. Bharath Rupireddy
  • Re: Add a hook for handling logical decoding messages on subscribers. Amit Kapila
• pg_walinspect: fix LSN validation messages and empty range handling Chao Li
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Kiran Kaki
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Chao Li
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Bharath Rupireddy
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Kiran Kaki
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Chao Li
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Kiran Kaki
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Chao Li
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Kiran Kaki
  • Re: pg_walinspect: fix LSN validation messages and empty range handling surya poondla
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Kiran Kaki
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Kiran Kaki
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Chao Li
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Kiran Kaki
  • Re: pg_walinspect: fix LSN validation messages and empty range handling Xuneng Zhou
  • Re: pg_walinspect: fix LSN validation messages and empty range handling surya poondla
• Re: test: avoid redundant standby catchup in 049_wait_for_lsn Xuneng Zhou
  • Re: test: avoid redundant standby catchup in 049_wait_for_lsn Xuneng Zhou
  • Re: test: avoid redundant standby catchup in 049_wait_for_lsn Jobin Augustine

• Earlier messages
• Later messages