pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #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]
BUG #17816: Invalid memory access in translate function
2023-03-01 08:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17816: Invalid memory access in translate function
2023-03-01 15:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Gpg error with Postgresql aarch64 repo - PG14
2023-03-01 12:40 UTC Felipe Die <felipedie@gmail.com>
Memory leakage in libpq valgrind test
2023-03-01 06:34 UTC Sudheer H R <sudheer.hr@tekenlight.com>
` Re: Memory leakage in libpq valgrind test
2023-03-01 06:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Memory leakage in libpq valgrind test
2023-03-01 06:59 UTC Michael Paquier <michael@paquier.xyz>
` Re: Memory leakage in libpq valgrind test
2023-03-01 07:05 UTC Sudheer H R <sudheer.hr@tekenlight.com>
[4+ messages in thread]
Crash during backend start when low on memory
2022-12-14 12:58 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2022-12-14 13:23 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Crash during backend start when low on memory
2022-12-14 15:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Crash during backend start when low on memory
2022-12-14 21:14 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2022-12-14 21:21 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2022-12-15 17:20 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Crash during backend start when low on memory
2022-12-16 08:46 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-13 10:05 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-13 11:53 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Crash during backend start when low on memory
2023-01-13 15:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Crash during backend start when low on memory
2023-01-16 10:09 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-16 20:52 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-16 20:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Crash during backend start when low on memory
2023-01-16 21:10 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-01-16 21:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Crash during backend start when low on memory
2023-02-05 21:00 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-02-05 23:18 UTC Andres Freund <andres@anarazel.de>
` Re: Crash during backend start when low on memory
2023-02-06 07:37 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-02-06 15:50 UTC Mats Kindahl <mats@timescale.com>
` Re: Crash during backend start when low on memory
2023-02-06 18:41 UTC Andres Freund <andres@anarazel.de>
` Re: Crash during backend start when low on memory
2023-02-28 20:39 UTC Mats Kindahl <mats@timescale.com>
[21+ messages in thread]
BUG #17814: Detail info on kerbos authentication
2023-02-28 18:44 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 15:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 16:28 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 16:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 17:31 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 17:54 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 18:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 18:06 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 18:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 18:41 UTC Cherio <cherio@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 19:29 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 19:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 20:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-27 20:36 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
2023-02-28 14:53 UTC Cherio <cherio@gmail.com>
[14+ messages in thread]
BUG #17813: I have an error about the installation of PostgreSQL installer on every version. please help.
2023-02-28 04:04 UTC PG Bug reporting form <noreply@postgresql.org>
Regarding backpatching to v14
2023-02-27 10:32 UTC niraj nandane <niraj.nandane@gmail.com>
` Re: Regarding backpatching to v14
2023-02-27 23:40 UTC Michael Paquier <michael@paquier.xyz>
[2+ messages in thread]
BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-01-10 07:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-01-13 09:36 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-01 02:47 UTC Bowen Shi <zxwsbg12138@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-01 15:32 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-02 07:45 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-21 03:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-21 06:22 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-21 07:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-22 10:27 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-24 00:36 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-24 11:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-24 19:56 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-25 03:39 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-25 20:38 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-27 00:08 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-27 03:01 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17744: Fail Assert while recoverying from pg_basebackup
2023-02-27 04:01 UTC Michael Paquier <michael@paquier.xyz>
[17+ messages in thread]
BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-18 08:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-20 22:49 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 04:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 05:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 17:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 19:33 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 20:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 20:17 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 20:42 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 20:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 22:16 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 22:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-21 23:33 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-22 00:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-22 01:17 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-22 19:23 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-22 21:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-23 18:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-23 21:00 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-23 22:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-23 23:36 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 01:54 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 17:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 17:44 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 17:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 22:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 22:53 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 23:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-24 23:57 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 19:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 20:19 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 20:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 21:46 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible fields that leads to a server crash
2023-02-25 21:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
[34+ messages in thread]
BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 09:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 11:56 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 15:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 17:15 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-21 18:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-22 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-22 09:07 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-22 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-22 12:29 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-23 11:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-23 12:00 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-23 21:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-23 23:20 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-24 08:50 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-24 16:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-25 15:08 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #17803: Rule "ALSO INSERT ... SELECT ..." fails to substitute default values
2023-02-25 16:00 UTC Alexander Lakhin <exclusion@gmail.com>
[17+ messages in thread]
two bugs
2023-02-25 01:43 UTC zhxpgh <zhxpgh@foxmail.com>
` Re: two bugs
2023-02-25 13:37 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
[2+ 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