pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #16631: postgres_fdw tries to insert into generated columns
2020-09-23 18:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16631: postgres_fdw tries to insert into generated columns
2021-07-03 10:44 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16631: postgres_fdw tries to insert into generated columns
2021-07-07 07:20 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16631: postgres_fdw tries to insert into generated columns
2021-07-07 08:44 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: BUG #16631: postgres_fdw tries to insert into generated columns
2021-07-07 09:35 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16631: postgres_fdw tries to insert into generated columns
2021-07-07 15:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16631: postgres_fdw tries to insert into generated columns
2021-07-12 20:36 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: BUG #16631: postgres_fdw tries to insert into generated columns
2021-07-15 09:15 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16631: postgres_fdw tries to insert into generated columns
2021-08-04 08:30 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16631: postgres_fdw tries to insert into generated columns
2021-08-05 11:19 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
[10+ messages in thread]
psql doesn't show tables duplicated in multiple schemas
2021-08-02 07:05 UTC Wojciech Strzalka <wstrzalka@gmail.com>
` Re: psql doesn't show tables duplicated in multiple schemas
2021-08-02 09:32 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: psql doesn't show tables duplicated in multiple schemas
2021-08-02 10:42 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: psql doesn't show tables duplicated in multiple schemas
2021-08-02 10:57 UTC Wojciech Strzalka <wstrzalka@gmail.com>
` Re: psql doesn't show tables duplicated in multiple schemas
2021-08-03 04:35 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: psql doesn't show tables duplicated in multiple schemas
2021-08-03 05:28 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: psql doesn't show tables duplicated in multiple schemas
2021-08-03 06:16 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: psql doesn't show tables duplicated in multiple schemas
2021-08-03 13:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: psql doesn't show tables duplicated in multiple schemas
2021-08-04 02:05 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[9+ messages in thread]
LOG: Failed to reopen the file pg_stat/global.stat retrying
2021-08-03 11:12 UTC sreekanth vajrapu <sreekanthvajrapu@gmail.com>
` Re: LOG: Failed to reopen the file pg_stat/global.stat retrying
2021-08-03 14:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17130: Error while executing request
2021-08-03 07:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17130: Error while executing request
2021-08-03 08:47 UTC Erik Rijkers <er@xs4all.nl>
` Re: BUG #17130: Error while executing request
2021-08-03 13:13 UTC Guillaume Lelarge <guillaume@lelarge.info>
` Re: BUG #17130: Error while executing request
2021-08-03 13:18 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17130: Error while executing request
2021-08-03 13:26 UTC Guillaume Lelarge <guillaume@lelarge.info>
` Re: BUG #17130: Error while executing request
2021-08-03 13:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #17129: Internal Error
2021-08-02 15:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17129: Internal Error
2021-08-02 18:09 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
Many queries stuck for waiting MultiXactOffsetControlLock on PostgreSQL 9.6.1 replica
2021-07-31 19:30 UTC Rui An <rueian.huang@gmail.com>
` Re: Many queries stuck for waiting MultiXactOffsetControlLock on PostgreSQL 9.6.1 replica
2021-08-02 04:57 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Many queries stuck for waiting MultiXactOffsetControlLock on PostgreSQL 9.6.1 replica
2021-08-02 05:48 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Many queries stuck for waiting MultiXactOffsetControlLock on PostgreSQL 9.6.1 replica
2021-08-02 14:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-13 09:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-14 02:12 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-14 07:52 UTC Marcin Krupowicz <marcin@071.ovh>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-14 23:10 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-15 05:22 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-15 07:33 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-15 08:59 UTC Marcin Krupowicz <marcin@071.ovh>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-15 16:09 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-15 16:11 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-15 19:09 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-15 20:49 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-15 21:33 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-16 02:05 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-16 02:49 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-16 16:13 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-16 18:09 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-17 14:28 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-19 02:13 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-19 21:24 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-20 04:18 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-28 15:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-29 07:20 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-29 07:45 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-29 07:50 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-07-29 21:19 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-08-02 06:00 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
2021-08-02 13:08 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[27+ messages in thread]
BUG #17128: minimum numeric 'integer' is -2147483647 not -2147483648 as documented
2021-07-29 22:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17128: minimum numeric 'integer' is -2147483647 not -2147483648 as documented
2021-07-30 15:05 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #17128: minimum numeric 'integer' is -2147483647 not -2147483648 as documented
2021-07-30 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17128: minimum numeric 'integer' is -2147483647 not -2147483648 as documented
2021-07-30 17:56 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #17128: minimum numeric 'integer' is -2147483647 not -2147483648 as documented
2021-07-30 19:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17128: minimum numeric 'integer' is -2147483647 not -2147483648 as documented
2021-07-30 20:44 UTC John Naylor <john.naylor@enterprisedb.com>
[6+ messages in thread]
The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-02 13:24 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-02 23:35 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-08 07:49 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-08 08:06 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-08 08:32 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-08 10:18 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-08 10:32 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-08 17:10 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-22 11:14 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-23 06:09 UTC Andrey V. Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-23 11:26 UTC Andrey V. Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-25 08:55 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-27 06:22 UTC Andrey V. Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-27 10:50 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-27 11:00 UTC Andrey V. Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-28 03:35 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-28 06:39 UTC Andrey V. Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-28 08:28 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-30 08:11 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
2021-07-30 12:25 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
[20+ messages in thread]
BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
2021-07-29 02:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
2021-07-29 03:35 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
2021-07-29 04:07 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
2021-07-29 04:14 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
2021-07-29 04:26 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
2021-07-29 04:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17127: drop column cann't delete from pg_attribute, so it will up to 1600 limits soon
2021-07-29 05:44 UTC David Rowley <dgrowleyml@gmail.com>
[7+ messages in thread]
BUG #17125: Operator precedence bug in websearch_to_tsquery function
2021-07-28 01:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17125: Operator precedence bug in websearch_to_tsquery function
2021-07-28 13:40 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17125: Operator precedence bug in websearch_to_tsquery function
2021-07-28 14:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes
2021-07-14 03:02 UTC Orishich Aleksey <a.orishich@cft.ru>
` RE: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes
2021-07-27 11:38 UTC Orishich Aleksey <a.orishich@cft.ru>
` Re: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes
2021-07-27 11:58 UTC Daniel Gustafsson <daniel@yesql.se>
` RE: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes
2021-07-28 02:17 UTC Orishich Aleksey <a.orishich@cft.ru>
[4+ messages in thread]
BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-20 21:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-22 07:52 UTC Neil Chen <carpenter.nail.cz@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-22 13:42 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-22 16:01 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-23 15:31 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-23 22:41 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-23 23:02 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-23 23:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-25 04:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-25 21:02 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-26 23:29 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-29 20:22 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-06-29 22:06 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-07-15 22:59 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-07-20 21:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-07-21 10:25 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-07-21 15:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-07-27 15:31 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-07-27 15:34 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-07-27 15:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-07-27 19:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
2021-07-27 21:12 UTC Alexander Korotkov <aekorotkov@gmail.com>
[22+ messages in thread]
BUG #17124: Psql prompting for a password
2021-07-27 14:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17124: Psql prompting for a password
2021-07-27 15:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17124: Psql prompting for a password
2021-07-27 17:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17124: Psql prompting for a password
2021-07-27 17:56 UTC Valdir Kageyama <vtkageyama@gmail.com>
[4+ messages in thread]
BUG #17123: ALTER TABLE ... NO INHERIT leaves orphaned statistics behind
2021-07-26 12:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17123: ALTER TABLE ... NO INHERIT leaves orphaned statistics behind
2021-07-26 14:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17123: ALTER TABLE ... NO INHERIT leaves orphaned statistics behind
2021-07-26 15:16 UTC Christoph Berg <christoph.berg@credativ.de>
[3+ messages in thread]
BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
2021-07-23 14:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
2021-07-23 16:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
2021-07-24 21:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
2021-07-25 09:34 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
2021-07-25 14:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
2021-07-25 15:54 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
2021-07-26 03:31 UTC Michael Paquier <michael@paquier.xyz>
[7+ messages in thread]
BUG #17073: docs - "Improve signal handling reliability"
2021-06-25 02:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17073: docs - "Improve signal handling reliability"
2021-06-29 01:02 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #17073: docs - "Improve signal handling reliability"
2021-07-01 00:54 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #17073: docs - "Improve signal handling reliability"
2021-07-01 01:17 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17073: docs - "Improve signal handling reliability"
2021-07-01 01:52 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #17073: docs - "Improve signal handling reliability"
2021-07-01 01:57 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17073: docs - "Improve signal handling reliability"
2021-07-01 02:41 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #17073: docs - "Improve signal handling reliability"
2021-07-01 06:30 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17073: docs - "Improve signal handling reliability"
2021-07-25 02:27 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
[9+ messages in thread]
BUG #17117: FailedAssertion at planner.c
2021-07-21 03:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17117: FailedAssertion at planner.c
2021-07-22 12:28 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17117: FailedAssertion at planner.c
2021-07-22 13:58 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17117: FailedAssertion at planner.c
2021-07-22 14:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-12 17:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-13 05:52 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-13 14:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-13 15:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-13 18:04 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-13 18:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-13 18:38 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-14 05:52 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-14 06:05 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-14 16:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-14 16:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-22 06:20 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped)
2021-07-22 14:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
[13+ messages in thread]
Re: BUG #16696: Backend crash in llvmjit
2020-11-02 21:45 UTC Dmitry Marakasov <amdmi3@amdmi3.ru>
` BUG #16696: Backend crash in llvmjit
2020-11-02 21:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16696: Backend crash in llvmjit
2020-11-03 00:00 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16696: Backend crash in llvmjit
2020-11-03 00:38 UTC Dmitry Marakasov <amdmi3@amdmi3.ru>
` Re: BUG #16696: Backend crash in llvmjit
2020-11-04 21:20 UTC Dmitry Marakasov <amdmi3@amdmi3.ru>
` Re: BUG #16696: Backend crash in llvmjit
2020-11-04 23:50 UTC Dmitry Marakasov <amdmi3@amdmi3.ru>
` Re: BUG #16696: Backend crash in llvmjit
2020-11-10 05:48 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16696: Backend crash in llvmjit
2020-11-16 00:45 UTC Dmitry Marakasov <amdmi3@amdmi3.ru>
` Re: BUG #16696: Backend crash in llvmjit
2021-05-19 14:49 UTC Palle <girgen@pingpong.net>
` Re: BUG #16696: Backend crash in llvmjit
2021-07-18 05:13 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #16696: Backend crash in llvmjit
2021-07-21 09:31 UTC Palle Girgensohn <girgen@pingpong.se>
` Re: BUG #16696: Backend crash in llvmjit
2021-07-21 16:59 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16696: Backend crash in llvmjit
2021-07-22 03:30 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #16696: Backend crash in llvmjit
2021-07-22 14:06 UTC Dmitry Marakasov <amdmi3@amdmi3.ru>
[14+ messages in thread]
BUG #17115: psqlODBC Unicode(x64) driver treats a boolean field as text
2021-07-20 19:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17115: psqlODBC Unicode(x64) driver treats a boolean field as text
2021-07-22 12:43 UTC John Naylor <john.naylor@enterprisedb.com>
[2+ messages in thread]
BUG #17114: postgresql odbc driver compilation
2021-07-19 09:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17114: postgresql odbc driver compilation
2021-07-22 12:42 UTC John Naylor <john.naylor@enterprisedb.com>
[2+ messages in thread]
BUG #17118: ALTER TABLE doesn't discard redundant UNIQUE constraints as CREATE TABLE will
2021-07-21 19:38 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17113: Assert failed on calling a function fixed after an extension reload
2021-07-18 21:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17113: Assert failed on calling a function fixed after an extension reload
2021-07-19 14:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17113: Assert failed on calling a function fixed after an extension reload
2021-07-19 23:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17077: about three parameters in postgresql 13.3
2021-06-30 06:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17077: about three parameters in postgresql 13.3
2021-07-17 04:40 UTC leiyanliang@highgo.com <leiyanliang@highgo.com>
` Re: BUG #17077: about three parameters in postgresql 13.3
2021-07-17 14:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17077: about three parameters in postgresql 13.3
2021-07-17 14:50 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #17077: about three parameters in postgresql 13.3
2021-07-17 15:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17077: about three parameters in postgresql 13.3
2021-07-17 17:24 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17077: about three parameters in postgresql 13.3
2021-07-17 19:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ 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