pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #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]
BUG #17824: PQTRANS_ACTIVE misleading
2023-03-08 04:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17824: PQTRANS_ACTIVE misleading
2023-03-08 16:22 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17824: PQTRANS_ACTIVE misleading
2023-03-08 16:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
2023-03-07 20:14 UTC Stephens, Gary <Gary.Stephens@ehi.com>
` Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
2023-03-07 21:32 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
2023-03-08 09:55 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
2023-03-08 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
2023-02-27 20:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
2023-02-27 21:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
2023-03-07 18:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
2023-03-08 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
[4+ messages in thread]
'CLUSTER' in one database prevents running it in two others on the same database cluster (PG15.2)
2023-03-05 21:38 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Fwd: 'CLUSTER' in one database prevents running it in two others on the same database cluster (PG15.2)
2023-03-06 06:46 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: 'CLUSTER' in one database prevents running it in two others on the same database cluster (PG15.2)
2023-03-07 11:25 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[3+ messages in thread]
BUG #17823: Generated columns not always updated correctly
2023-03-06 07:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17823: Generated columns not always updated correctly
2023-03-06 16:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17823: Generated columns not always updated correctly
2023-03-06 21:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2021-07-20 21:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2021-07-23 12:56 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2021-07-26 07:36 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2021-07-26 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2021-07-27 11:17 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2021-07-27 21:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2021-07-28 05:02 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2021-07-29 21:41 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2021-07-30 05:48 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2022-01-09 17:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2022-01-15 05:41 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2022-01-16 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2023-03-05 09:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2023-03-06 03:52 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
2023-03-06 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
[15+ messages in thread]
found a possible bug, modulus of an integer on a partition table appears to be wrong
2023-03-05 18:45 UTC Howard A. Chou <maingroup@yahoo.com>
` Re: found a possible bug, modulus of an integer on a partition table appears to be wrong
2023-03-05 23:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17822: Some scripts are blocked by Device Guard
2023-03-05 04:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17822: Some scripts are blocked by Device Guard
2023-03-05 23:18 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-01 19:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-01 20:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 11:21 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 14:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 18:17 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 18:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
2023-03-03 19:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[8+ messages in thread]
BUG #17819: The assert failed #17334 has not been repaired
2023-03-02 11:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17819: The assert failed #17334 has not been repaired
2023-03-02 16:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17818: CTE is not returning the right data.
2023-03-02 08:33 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #17818: CTE is not returning the right data.
2023-03-02 13:28 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17818: CTE is not returning the right data.
2023-03-02 15:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-01 05:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-01 09:31 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-01 11:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-02 05:05 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-02 06:14 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #17815: Server crashes on executing gist_page_items() in pageinspect extension
2023-03-02 07:02 UTC Michael Paquier <michael@paquier.xyz>
[6+ messages in thread]
BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-02-28 03:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-02-28 13:52 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 02:01 UTC Keyerror Smart <smartkeyerror@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 02:52 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 03:02 UTC Keyerror Smart <smartkeyerror@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 03:40 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 04:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 04:55 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 06:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 07:15 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 13:22 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 15:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
2023-03-01 16:35 UTC David G. Johnston <david.g.johnston@gmail.com>
[13+ 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