pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17596: "invalid attribute number 11" when updating partitioned table with a MULTIEXPR_SUBLINK
2022-08-26 04:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17596: "invalid attribute number 11" when updating partitioned table with a MULTIEXPR_SUBLINK
2022-08-26 23:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17593: min key size 112 bits from FIPS SP800-131 requirement for HMAC-SHA raises exception in SCRAM-SHA-256
2022-08-25 17:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17593: min key size 112 bits from FIPS SP800-131 requirement for HMAC-SHA raises exception in SCRAM-SHA-256
2022-08-26 00:22 UTC Scott Zelenka <szelenka@gmail.com>
[2+ messages in thread]
Buggy results from current_role in a "security invoker" trigger function in a multi-owner, "cascade delete via FK" scenario
2022-08-24 04:19 UTC Bryn Llewellyn <bryn@yugabyte.com>
BUG #17580: use pg_terminate_backend to terminate a wal sender process may wait a long time
2022-08-10 08:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17580: use pg_terminate_backend to terminate a wal sender process may wait a long time
2022-08-12 03:28 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17580: use pg_terminate_backend to terminate a wal sender process may wait a long time
2022-08-15 02:27 UTC 巨鲸 <13207961@qq.com>
` Re: BUG #17580: use pg_terminate_backend to terminate a wal sender process may wait a long time
2022-08-15 04:02 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re:Re: BUG #17580: use pg_terminate_backend to terminate a wal senderprocess may wait a long time
2022-08-16 03:26 UTC 巨鲸 <13207961@qq.com>
` Re: BUG #17580: use pg_terminate_backend to terminate a wal sender process may wait a long time
2022-08-23 04:00 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17580: use pg_terminate_backend to terminate a wal sender process may wait a long time
2022-08-23 11:00 UTC Amit Kapila <amit.kapila16@gmail.com>
[7+ messages in thread]
BUG #17585: Wrong path to the extension control file
2022-08-12 20:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17585: Wrong path to the extension control file
2022-08-12 22:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [External] Re: BUG #17585: Wrong path to the extension control file
2022-08-22 13:16 UTC Garbuz, Yakov [ASM Research] <Yakov.Garbuz@asmr.com>
` Re: [External] Re: BUG #17585: Wrong path to the extension control file
2022-08-22 13:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #17591: elog(ERROR) cause SharedSnapshotLock deadlock
2022-08-22 06:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17591: elog(ERROR) cause SharedSnapshotLock deadlock
2022-08-22 07:45 UTC Zhang Mingli <zmlpostgres@gmail.com>
` Re: BUG #17591: elog(ERROR) cause SharedSnapshotLock deadlock
2022-08-22 13:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17543: CSVLOG malformed from disk space error
2022-07-09 16:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17543: CSVLOG malformed from disk space error
2022-07-11 12:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17543: CSVLOG malformed from disk space error
2022-07-13 00:26 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17543: CSVLOG malformed from disk space error
2022-07-13 00:48 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17543: CSVLOG malformed from disk space error
2022-07-13 04:09 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17543: CSVLOG malformed from disk space error
2022-08-21 19:07 UTC Noah Misch <noah@leadboat.com>
[6+ messages in thread]
BUG #17590: [OPTIMIZER] DELETE never ends on a small table, found a workaround which makes it instant
2022-08-19 15:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17590: [OPTIMIZER] DELETE never ends on a small table, found a workaround which makes it instant
2022-08-19 16:17 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
[2+ messages in thread]
= TRUE vs IS TRUE confuses partition index creation
2022-08-16 21:33 UTC Christophe Pettus <xof@thebuild.com>
` Re: = TRUE vs IS TRUE confuses partition index creation
2022-08-16 21:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: = TRUE vs IS TRUE confuses partition index creation
2022-08-17 04:27 UTC Richard Guo <guofenglinux@gmail.com>
` Re: = TRUE vs IS TRUE confuses partition index creation
2022-08-17 07:16 UTC Richard Guo <guofenglinux@gmail.com>
` Re: = TRUE vs IS TRUE confuses partition index creation
2022-08-17 21:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: = TRUE vs IS TRUE confuses partition index creation
2022-08-18 02:27 UTC Richard Guo <guofenglinux@gmail.com>
` Re: = TRUE vs IS TRUE confuses partition index creation
2022-08-18 16:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ messages in thread]
BUG #17589: Invalid read at array_positions
2022-08-17 12:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17589: Invalid read at array_positions
2022-08-17 13:24 UTC Robins Tharakan <tharakan@gmail.com>
[2+ messages in thread]
BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-01 14:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-01 22:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-02 08:49 UTC Martijn van Oosterhout <kleptog@gmail.com>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-02 11:28 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-03 07:45 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-03 14:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-03 14:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-03 19:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-03 21:12 UTC Martijn van Oosterhout <kleptog@gmail.com>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-03 21:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-03 21:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-04 01:05 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-04 01:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-04 03:16 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-04 14:41 UTC Martijn van Oosterhout <kleptog@gmail.com>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-04 15:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-04 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
2022-08-17 10:34 UTC Dmitry Dolgov <9erthalion6@gmail.com>
[18+ messages in thread]
BUG #17588: RHEL 8 nothing provides libarmadillo.so.10 (64bit) needed by gdal-libs3x*
2022-08-15 20:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17588: RHEL 8 nothing provides libarmadillo.so.10 (64bit) needed by gdal-libs3x*
2022-08-16 10:04 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #17588: RHEL 8 nothing provides libarmadillo.so.10 (64bit) needed by gdal-libs3x*
2022-08-16 20:39 UTC Marcelo Marques <marcelosmbr@gmail.com>
` Re: BUG #17588: RHEL 8 nothing provides libarmadillo.so.10 (64bit) needed by gdal-libs3x*
2022-08-17 08:19 UTC Devrim Gündüz <devrim@gunduz.org>
[4+ messages in thread]
(no subject)
2012-08-23 15:26 UTC Nupus Cs <csnupus@gmail.com>
` No-op updates with partitioning and logical replication started failing in version 13
2022-08-03 20:53 UTC Brad Nicholson <brad.nicholson@instacart.com>
` RE: No-op updates with partitioning and logical replication started failing in version 13
2022-08-04 09:29 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: No-op updates with partitioning and logical replication started failing in version 13
2022-08-04 12:19 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: No-op updates with partitioning and logical replication started failing in version 13
2022-08-05 09:30 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: No-op updates with partitioning and logical replication started failing in version 13
2022-08-15 03:46 UTC Peter Smith <smithpb2250@gmail.com>
` RE: No-op updates with partitioning and logical replication started failing in version 13
2022-08-15 05:37 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: No-op updates with partitioning and logical replication started failing in version 13
2022-08-16 02:59 UTC Peter Smith <smithpb2250@gmail.com>
` Re: No-op updates with partitioning and logical replication started failing in version 13
2022-08-16 06:58 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: No-op updates with partitioning and logical replication started failing in version 13
2022-08-16 07:49 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: No-op updates with partitioning and logical replication started failing in version 13
2022-08-16 10:37 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: No-op updates with partitioning and logical replication started failing in version 13
2022-08-16 10:38 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: No-op updates with partitioning and logical replication started failing in version 13
2022-08-17 04:40 UTC Amit Langote <amitlangote09@gmail.com>
` Re: No-op updates with partitioning and logical replication started failing in version 13
2022-08-17 06:40 UTC Amit Kapila <amit.kapila16@gmail.com>
[14+ messages in thread]
BUG #17586: Look like there are an another bug in REINDEX INDEX CONCURRENTLY of pg_toast indexes
2022-08-15 11:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17586: Look like there are an another bug in REINDEX INDEX CONCURRENTLY of pg_toast indexes
2022-08-15 23:01 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17586: Look like there are an another bug in REINDEX INDEX CONCURRENTLY of pg_toast indexes
2022-08-16 08:34 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #17586: Look like there are an another bug in REINDEX INDEX CONCURRENTLY of pg_toast indexes
2022-08-17 01:18 UTC Andres Freund <andres@anarazel.de>
[4+ messages in thread]
[PATCH] Fix segfault calling PQflush on invalid connection
2022-08-15 00:44 UTC Daniele Varrazzo <daniele.varrazzo@gmail.com>
` Re: [PATCH] Fix segfault calling PQflush on invalid connection
2022-08-15 01:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [PATCH] Fix segfault calling PQflush on invalid connection
2022-08-15 11:20 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: [PATCH] Fix segfault calling PQflush on invalid connection
2022-08-15 14:57 UTC Daniele Varrazzo <daniele.varrazzo@gmail.com>
` Re: [PATCH] Fix segfault calling PQflush on invalid connection
2022-08-15 15:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [PATCH] Fix segfault calling PQflush on invalid connection
2022-08-16 16:08 UTC Francisco Olarte <folarte@peoplecall.com>
[6+ messages in thread]
BUG #17568: unexpected zero page at block 0 during REINDEX CONCURRENTLY
2022-08-03 14:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #17568: unexpected zero page at block 0 during REINDEX CONCURRENTLY
2022-08-15 14:02 UTC Sergei Kornilov <sk@zsrv.org>
` Re: BUG #17568: unexpected zero page at block 0 during REINDEX CONCURRENTLY
2022-08-15 23:39 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17568: unexpected zero page at block 0 during REINDEX CONCURRENTLY
2022-08-15 23:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17568: unexpected zero page at block 0 during REINDEX CONCURRENTLY
2022-08-16 00:10 UTC Andres Freund <andres@anarazel.de>
[5+ messages in thread]
BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-12 14:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-12 19:25 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-13 21:48 UTC James Inform <james.inform@pharmapp.de>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-13 22:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 00:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 02:43 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 03:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 03:55 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 04:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 06:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 06:31 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 14:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 16:17 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation
2022-08-14 16:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[14+ messages in thread]
BUG #17582: Error: Package: gdal-libs-1.11.4-12.rhel7.x86_64 (@pgdg11)
2022-08-11 15:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17582: Error: Package: gdal-libs-1.11.4-12.rhel7.x86_64 (@pgdg11)
2022-08-14 14:27 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #17583: Server crashes on executing CROSS JOIN with very big number of tables
2022-08-12 06:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17583: Server crashes on executing CROSS JOIN with very big number of tables
2022-08-12 09:03 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17583: Server crashes on executing CROSS JOIN with very big number of tables
2022-08-12 09:22 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17583: Server crashes on executing CROSS JOIN with very big number of tables
2022-08-13 19:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #17581: DB Restriction Option Is Not Working
2022-08-11 11:40 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17581: DB Restriction Option Is Not Working
2022-08-12 07:19 UTC John Naylor <john.naylor@enterprisedb.com>
[2+ messages in thread]
BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-07 21:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-08 02:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-11 02:41 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-11 11:40 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-11 13:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-11 14:17 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-11 14:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-11 16:27 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-11 17:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE
2022-08-12 00:58 UTC Richard Guo <guofenglinux@gmail.com>
[10+ messages in thread]
BUG #17206: the function array_cat(anyarray, anyarray) does not exist
2021-09-30 20:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17206: the function array_cat(anyarray, anyarray) does not exist
2021-09-30 22:49 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17206: the function array_cat(anyarray, anyarray) does not exist
2021-09-30 23:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17206: the function array_cat(anyarray, anyarray) does not exist
2021-10-01 19:36 UTC Edouard HIBON <edouard.hibon@free.fr>
` Re: BUG #17206: the function array_cat(anyarray, anyarray) does not exist
2022-08-11 10:17 UTC David Turoň <Turon.David@seznam.cz>
` Re: BUG #17206: the function array_cat(anyarray, anyarray) does not exist
2022-08-11 11:08 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #17206: the function array_cat(anyarray, anyarray) does not exist
2022-08-11 13:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ messages in thread]
Psql utf8
2022-08-11 11:28 UTC Andrea Spanu <andreaspanu80@gmail.com>
Getting "invalid cache ID: 42" in pg10.5
2018-09-20 07:35 UTC pcsuccess@sina.com
` Re: Getting "invalid cache ID: 42" in pg10.5
2018-09-20 09:57 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` [PATCH] Reject MERGE in CTE
2022-08-11 11:17 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[3+ messages in thread]
[PATCH v2] Reject MERGE in CTEs and COPY
2022-08-11 11:17 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[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