agora inbox for pgsql-bugs@postgresql.org  
help / color / mirror / Atom feed
Should CUSTER (ANALYZE) work?
  2026-07-21 21:36 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Should CUSTER (ANALYZE) work?
  2026-08-12 19:50 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Should CUSTER (ANALYZE) work?
  2026-08-13 20:38 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: Should CUSTER (ANALYZE) work?
  2026-08-15 09:12 UTC  Alvaro Herrera <alvherre@kurilemu.de>
  [4+ messages in thread]

BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-02 13:04 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-02 13:54 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-02 14:06 UTC  =?windows-1250?Q?Adrian_M=F6nnich?= <adrian.moennich@cern.ch>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-02 14:27 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-02 14:49 UTC  Adrian Mönnich <adrian.moennich@cern.ch>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-02 18:12 UTC  Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-02 19:00 UTC  Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-02 22:34 UTC  Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-02 22:43 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-04 14:45 UTC  Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-16 05:25 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-04-16 18:52 UTC  Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-05-19 10:10 UTC  Adrian Mönnich <adrian.moennich@cern.ch>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-08-14 15:10 UTC  Adrian Mönnich <adrian.moennich@cern.ch>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
  2026-08-14 19:11 UTC  Tomas Vondra <tomas@vondra.me>
  [15+ messages in thread]

BUG #19619: WHERE scale(n) = 1 pushed past GROUP BY / window PARTITION BY, wrong COUNT
  2026-08-14 17:41 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19619: WHERE scale(n) = 1 pushed past GROUP BY / window PARTITION BY, wrong COUNT
  2026-08-14 18:30 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19619: WHERE scale(n) = 1 pushed past GROUP BY / window PARTITION BY, wrong COUNT
  2026-08-14 18:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

COPY TO regression with psql -c
  2026-08-11 19:32 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: COPY TO regression with psql -c
  2026-08-12 08:37 UTC  Christoph Berg <myon@debian.org>
` Re: COPY TO regression with psql -c
  2026-08-12 17:58 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: COPY TO regression with psql -c
  2026-08-12 19:53 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: COPY TO regression with psql -c
  2026-08-13 20:44 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: COPY TO regression with psql -c
  2026-08-13 22:52 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: COPY TO regression with psql -c
  2026-08-14 16:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [7+ messages in thread]

DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
  2026-07-22 18:43 UTC  Zsolt Parragi <zsolt.parragi@percona.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
  2026-07-29 05:30 UTC  solai v <solai.cdac@gmail.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
  2026-08-12 21:30 UTC  Melanie Plageman <melanieplageman@gmail.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
  2026-08-12 23:18 UTC  Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
  2026-08-13 09:23 UTC  Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
  2026-08-14 12:01 UTC  Peter Eisentraut <peter@eisentraut.org>
  [6+ messages in thread]

BUG #19617: Hash node can report incorrect actual rows number
  2026-08-12 23:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19617: Hash node can report incorrect actual rows number
  2026-08-13 17:36 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
  [2+ messages in thread]

pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found
  2026-08-12 10:50 UTC  Holger Jakobs <holger@jakobs.com>
` Re: pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found
  2026-08-12 15:14 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found
  2026-08-13 12:37 UTC  Michael Banck <mbanck@gmx.net>
  [3+ messages in thread]

BUG #19618: postgresql18 client package not found
  2026-08-13 10:47 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #19615: COVAR_POP / COVAR_SAMP / REGR_SXY return 0.0 instead of NaN
  2026-08-11 02:34 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19615: COVAR_POP / COVAR_SAMP / REGR_SXY return 0.0 instead of NaN
  2026-08-11 15:24 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19615: COVAR_POP / COVAR_SAMP / REGR_SXY return 0.0 instead of NaN
  2026-08-11 15:56 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19615: COVAR_POP / COVAR_SAMP / REGR_SXY return 0.0 instead of NaN
  2026-08-12 16:50 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

Re: BUG #19610: Database won't start if an unrelated process is exist
  2026-08-12 11:26 UTC  Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19610: Database won't start if an unrelated process is exist
  2026-08-12 12:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-06-24 21:57 UTC  Jacob Champion <jacob.champion@enterprisedb.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-06-26 00:12 UTC  Jacob Champion <jacob.champion@enterprisedb.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-07-06 11:03 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-07-08 22:54 UTC  Jacob Champion <jacob.champion@enterprisedb.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-07-09 14:48 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
  2026-08-10 11:41 UTC  Kirill Reshke <reshkekirill@gmail.com>
  [6+ messages in thread]

PostgreSQL 18.4 backend SIGSEGV in pgstat_gc_entry_refs() after caught DSM attach error
  2026-08-05 11:56 UTC  Niall Newman <nn@turacolabs.com>
` Re: PostgreSQL 18.4 backend SIGSEGV in pgstat_gc_entry_refs() after caught DSM attach error
  2026-08-09 23:42 UTC  Michael Paquier <michael@paquier.xyz>
  [2+ messages in thread]

file corruption goes undetected
  2026-08-06 14:11 UTC  Bram van der Vos <bram.van.der.vos@axisinto.nl>
` Re: file corruption goes undetected
  2026-08-06 22:01 UTC  Tomas Vondra <tomas@vondra.me>
` Re: file corruption goes undetected
  2026-08-06 22:09 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

Update in check_max_stack_depth
  2026-08-06 13:31 UTC  Daria Shanina <vilensipkdm@gmail.com>
` Re: Update in check_max_stack_depth
  2026-08-06 14:21 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [2+ messages in thread]

BUG #19555: TRAP: failed Assert (ent->cmin == change->data.tuplecid.cmin) on logical replication
  2026-07-17 03:55 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19555: TRAP: failed Assert (ent->cmin == change->data.tuplecid.cmin) on logical replication
  2026-07-17 18:24 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19555: TRAP: failed Assert (ent->cmin == change->data.tuplecid.cmin) on logical replication
  2026-08-06 12:06 UTC  li kid <lucian1412@outlook.com>
  [3+ messages in thread]

BUG #19608: Error while Reindexing Main Table
  2026-08-03 09:54 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19608: Error while Reindexing Main Table
  2026-08-06 05:43 UTC  Michael Paquier <michael@paquier.xyz>
  [2+ messages in thread]

BUG #19609: Server crashes when executing a JIT-compiled SQL function on s390x
  2026-08-04 12:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19609: Server crashes when executing a JIT-compiled SQL function on s390x
  2026-08-05 11:20 UTC  Артём Зарубин <a.prototype7@gmail.com>
` Re: BUG #19609: Server crashes when executing a JIT-compiled SQL function on s390x
  2026-08-05 14:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19609: Server crashes when executing a JIT-compiled SQL function on s390x
  2026-08-05 20:04 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19609: Server crashes when executing a JIT-compiled SQL function on s390x
  2026-08-05 22:43 UTC  John Naylor <johncnaylorls@gmail.com>
  [5+ messages in thread]

BUG #19588: Semantically equivalent DISTINCT ON query returns different result when wrapped in MATERIALIZED CTE.
  2026-07-30 09:56 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19588: Semantically equivalent DISTINCT ON query returns different result when wrapped in MATERIALIZED CTE.
  2026-08-05 13:54 UTC  Nitin Motiani <nitinmotiani@google.com>
  [2+ messages in thread]

BUG #19607: Bug 18: `pg_surgery` infinite loop in `heap_force_common`
  2026-08-03 08:40 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19607: Bug 18: `pg_surgery` infinite loop in `heap_force_common`
  2026-08-03 13:35 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19607: Bug 18: `pg_surgery` infinite loop in `heap_force_common`
  2026-08-03 13:44 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19607: Bug 18: `pg_surgery` infinite loop in `heap_force_common`
  2026-08-03 14:08 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19607: Bug 18: `pg_surgery` infinite loop in `heap_force_common`
  2026-08-04 09:48 UTC  Álvaro Herrera <alvherre@kurilemu.de>
  [5+ messages in thread]

BUG #19491: Segmentation fault triggered by IS NULL
  2026-05-22 06:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19491: Segmentation fault triggered by IS NULL
  2026-05-25 15:12 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19491: Segmentation fault triggered by IS NULL
  2026-05-25 16:36 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19491: Segmentation fault triggered by IS NULL
  2026-06-05 16:11 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19491: Segmentation fault triggered by IS NULL
  2026-06-06 06:27 UTC  Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19491: Segmentation fault triggered by IS NULL
  2026-06-08 18:40 UTC  Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19491: Segmentation fault triggered by IS NULL
  2026-06-11 14:27 UTC  Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19491: Segmentation fault triggered by IS NULL
  2026-08-04 03:25 UTC  =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19491: Segmentation fault triggered by IS NULL
  2026-08-04 09:29 UTC  Álvaro Herrera <alvherre@kurilemu.de>
  [9+ messages in thread]

BUG #19484: Segmentation fault triggered by FDW
  2026-05-18 06:38 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-05-20 12:37 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-05-20 17:46 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-05-22 20:56 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-05-30 06:18 UTC  Rafia Sabih <rafia.pghackers@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-09 15:10 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-10 05:15 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-10 11:08 UTC  Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-10 13:09 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-10 13:27 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-11 10:40 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-11 10:44 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-18 09:15 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-18 10:50 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-18 10:55 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-18 10:57 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-19 11:59 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-22 08:28 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-23 08:27 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 00:00 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 01:43 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 01:53 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 02:23 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 03:50 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 04:25 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 09:15 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 11:20 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 17:02 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-24 23:24 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-25 06:15 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-25 11:47 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-06-25 12:21 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-08-04 03:24 UTC  =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19484: Segmentation fault triggered by FDW
  2026-08-04 07:56 UTC  Amit Langote <amitlangote09@gmail.com>
  [34+ messages in thread]

BUG #19586: money division overflow
  2026-07-29 17:41 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19586: money division overflow
  2026-08-04 06:02 UTC  David Rowley <dgrowleyml@gmail.com>
  [2+ messages in thread]

BUG #19601: Vuln45: Unbounded recursion via self-retying Perl scalar in bool_plperl's SvTRUE call causes backend
  2026-08-03 06:54 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19601: Vuln45: Unbounded recursion via self-retying Perl scalar in bool_plperl's SvTRUE call causes backend
  2026-08-03 21:10 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19601: Vuln45: Unbounded recursion via self-retying Perl scalar in bool_plperl's SvTRUE call causes backend
  2026-08-03 22:01 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19601: Vuln45: Unbounded recursion via self-retying Perl scalar in bool_plperl's SvTRUE call causes backend
  2026-08-04 04:57 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [4+ messages in thread]

BUG #19600: pgcrypto crypt() can return text with invalid encoding
  2026-08-03 05:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19600: pgcrypto crypt() can return text with invalid encoding
  2026-08-03 15:26 UTC  Andrey Rachitskiy <pl0h0yp1@gmail.com>
  [2+ messages in thread]

BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-08-03 07:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin
  2026-08-03 13:16 UTC  Ayush Tiwari <ayushtiwari.slg01@gmail.com>
  [2+ messages in thread]


[next (older)]

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox