pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedCertificate expired
2023-03-15 17:42 UTC Sylvie Greverend <SGreverend@harriscomputer.com>
` Re: Certificate expired
2023-03-15 18:52 UTC Magnus Hagander <magnus@hagander.net>
` Re:Certificate expired
2023-03-15 19:00 UTC Sergei Kornilov <sk@zsrv.org>
[3+ messages in thread]
Merge command is erroring with: PlaceHolderVar found where not expected
2023-03-15 12:24 UTC Önder Kalacı <onderkalaci@gmail.com>
` Re: Merge command is erroring with: PlaceHolderVar found where not expected
2023-03-15 14:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-14 01:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-14 22:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-15 01:17 UTC Thiago Nunes <thiagotnunes@gmail.com>
` Re: BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-15 01:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17839: Heap-buffer overflow on float8_to_char with invalid template
2023-03-15 02:02 UTC Thiago Nunes <thiagotnunes@gmail.com>
[5+ messages in thread]
BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 15:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 16:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 18:19 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 18:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 19:26 UTC David G. Johnston <david.g.johnston@gmail.com>
[5+ messages in thread]
AW: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 18:12 UTC Hans Buschmann <buschmann@nidsa.net>
` AW: BUG #17842: Adding a qual to a working query gets bogus syntax error
2023-03-14 19:07 UTC Hans Buschmann <buschmann@nidsa.net>
[2+ messages in thread]
BUG #17843: Writing uninitialised data in logtape/buffile
2023-03-14 18:00 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17841: COPY Command Invalid QUOTES
2023-03-14 14:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17841: COPY Command Invalid QUOTES
2023-03-14 15:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
ERROR: PlaceHolderVar found where not expected
2023-03-14 03:01 UTC Richard Guo <guofenglinux@gmail.com>
` Re: ERROR: PlaceHolderVar found where not expected
2023-03-14 03:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: ERROR: PlaceHolderVar found where not expected
2023-03-14 03:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: ERROR: PlaceHolderVar found where not expected
2023-03-14 06:08 UTC Richard Guo <guofenglinux@gmail.com>
` Re: ERROR: PlaceHolderVar found where not expected
2023-03-14 15:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
Invalid memory allocation error with pg_recvlogical or with libPQ logical connection
2023-03-13 07:01 UTC jitesh tiwari <jitesh120@gmail.com>
` Re: Invalid memory allocation error with pg_recvlogical or with libPQ logical connection
2023-03-13 11:43 UTC Arne Roland <A.Roland@index.de>
` Re: Invalid memory allocation error with pg_recvlogical or with libPQ logical connection
2023-03-14 06:07 UTC jitesh tiwari <jitesh120@gmail.com>
[3+ messages in thread]
BUG #17837: The potential risks associated with executing "commit" in a procedure.
2023-03-13 12:40 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17837: The potential risks associated with executing "commit" in a procedure.
2023-03-13 20:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17835: Two assertions failed in nodeAgg.c and execExprInterp.c with the same SQL
2023-03-13 02:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17835: Two assertions failed in nodeAgg.c and execExprInterp.c with the same SQL
2023-03-13 15:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17835: Two assertions failed in nodeAgg.c and execExprInterp.c with the same SQL
2023-03-13 16:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
disable pipeline mode
2023-03-13 08:44 UTC Oleksandr Volkovskyi <oleksandr.volkovskyi@modulrfinance.com>
` Re: disable pipeline mode
2023-03-13 15:49 UTC Daniel Verite <daniel@manitou-mail.org>
[2+ messages in thread]
BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 07:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 11:29 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 12:05 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 13:22 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-14 19:19 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-15 09:41 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-02-15 19:42 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
2023-03-13 11:46 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[9+ messages in thread]
BUG #17809: MERGE ... UPDATE fails with BEFORE ROW UPDATE trigger when target row updated concurrently
2023-02-26 10:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17809: MERGE ... UPDATE fails with BEFORE ROW UPDATE trigger when target row updated concurrently
2023-02-27 12:07 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17809: MERGE ... UPDATE fails with BEFORE ROW UPDATE trigger when target row updated concurrently
2023-03-07 11:50 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17809: MERGE ... UPDATE fails with BEFORE ROW UPDATE trigger when target row updated concurrently
2023-03-09 13:11 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17809: MERGE ... UPDATE fails with BEFORE ROW UPDATE trigger when target row updated concurrently
2023-03-11 18:12 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17809: MERGE ... UPDATE fails with BEFORE ROW UPDATE trigger when target row updated concurrently
2023-03-12 11:14 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17809: MERGE ... UPDATE fails with BEFORE ROW UPDATE trigger when target row updated concurrently
2023-03-13 11:42 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[7+ messages in thread]
BUG #17836: Why does pg_dump need to add * to dump the full partition table structure
2023-03-13 07:44 UTC PG Bug reporting form <noreply@postgresql.org>
psql 14.7/15.2 report a bogus syntax error on function and procedure files that use BEGIN ATOMIC
2023-03-13 04:20 UTC David Adams <dpadams@gmail.com>
` Re: psql 14.7/15.2 report a bogus syntax error on function and procedure files that use BEGIN ATOMIC
2023-03-13 04:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: psql 14.7/15.2 report a bogus syntax error on function and procedure files that use BEGIN ATOMIC
2023-03-13 04:47 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: psql 14.7/15.2 report a bogus syntax error on function and procedure files that use BEGIN ATOMIC
2023-03-13 04:49 UTC David Adams <dpadams@gmail.com>
` Re: psql 14.7/15.2 report a bogus syntax error on function and procedure files that use BEGIN ATOMIC
2023-03-13 04:56 UTC David Adams <dpadams@gmail.com>
` Re: psql 14.7/15.2 report a bogus syntax error on function and procedure files that use BEGIN ATOMIC
2023-03-13 04:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: psql 14.7/15.2 report a bogus syntax error on function and procedure files that use BEGIN ATOMIC
2023-03-13 05:04 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: psql 14.7/15.2 report a bogus syntax error on function and procedure files that use BEGIN ATOMIC
2023-03-13 05:07 UTC David Adams <dpadams@gmail.com>
` Re: psql 14.7/15.2 report a bogus syntax error on function and procedure files that use BEGIN ATOMIC
2023-03-13 05:19 UTC David Adams <dpadams@gmail.com>
[9+ messages in thread]
BUG #17834: Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8))
2023-03-13 02:14 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17832: ERROR: failed to apply nullingrels to a non-Var in HEAD
2023-03-11 18:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17832: ERROR: failed to apply nullingrels to a non-Var in HEAD
2023-03-12 17:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17830: Incorrect memory access in trgm_regexp
2023-03-11 08:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17830: Incorrect memory access in trgm_regexp
2023-03-11 16:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17830: Incorrect memory access in trgm_regexp
2023-03-12 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
[3+ messages in thread]
BUG #17831: server crash
2023-03-11 08:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17831: server crash
2023-03-11 15:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17827: Rule on insert into table doesn't work when excepting select from the table itself
2023-03-09 10:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17827: Rule on insert into table doesn't work when excepting select from the table itself
2023-03-09 15:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17827: Rule on insert into table doesn't work when excepting select from the table itself
2023-03-10 08:18 UTC Hanna Yanchurevich <hyanchurevich@spotware.com>
` Re: BUG #17827: Rule on insert into table doesn't work when excepting select from the table itself
2023-03-10 14:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
unaccent fails when datlocprovider=i and datctype=C
2023-03-08 05:49 UTC Jeff Davis <pgsql@j-davis.com>
` Re: unaccent fails when datlocprovider=i and datctype=C
2023-03-10 08:40 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
[2+ messages in thread]
PostgreSQL 14.7 "ALTER TABLE IF EXISTS" fails - ERROR: schema/relation "<name>" does not exist
2023-03-09 13:00 UTC Salavessa, Joao (Senior Developer) <Joao.Salavessa@sky.uk>
` Re: PostgreSQL 14.7 "ALTER TABLE IF EXISTS" fails - ERROR: schema/relation "<name>" does not exist
2023-03-09 14:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: [EXTERNAL] Re: PostgreSQL 14.7 "ALTER TABLE IF EXISTS" fails - ERROR: schema/relation "<name>" does not exist
2023-03-09 15:33 UTC Salavessa, Joao (Senior Developer) <Joao.Salavessa@sky.uk>
[3+ messages in thread]
BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-01 09:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-01 14:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-01 20:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-02 05:40 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-02 05:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-02 08:38 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-06 14:31 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-06 15:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-06 15:43 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-02-06 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
2023-03-09 10:42 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[11+ messages in thread]
BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2022-01-15 08:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2022-01-15 16:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-06 03:02 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-06 23:39 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-06 23:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-07 01:14 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-07 01:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-08 11:57 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-08 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-08 20:50 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-09 04:39 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
2023-03-09 09:00 UTC Alexander Lakhin <exclusion@gmail.com>
[12+ messages in thread]
[next (older)]
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox