pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedQuery execution failure
2023-01-25 19:58 UTC Pete Storer <Pete.Storer@sas.com>
` Re: Query execution failure
2023-01-25 20:20 UTC Christophe Pettus <xof@thebuild.com>
` FW: Query execution failure
2023-01-25 22:17 UTC Pete Storer <Pete.Storer@sas.com>
` Re: FW: Query execution failure
2023-01-26 15:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: FW: Query execution failure
2023-01-26 15:43 UTC Pete Storer <Pete.Storer@sas.com>
` Re: FW: Query execution failure
2023-01-26 16:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: FW: Query execution failure
2023-01-30 15:34 UTC Bruce Momjian <bruce@momjian.us>
` Re: FW: Query execution failure
2023-01-30 16:16 UTC Joe Conway <mail@joeconway.com>
` Re: FW: Query execution failure
2023-01-30 16:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: FW: Query execution failure
2023-01-30 18:17 UTC Pete Storer <Pete.Storer@sas.com>
` Re: Query execution failure
2023-01-30 18:20 UTC Christophe Pettus <xof@thebuild.com>
` RE: Query execution failure
2023-01-30 18:24 UTC Pete Storer <Pete.Storer@sas.com>
` Re: Query execution failure
2023-01-30 20:04 UTC Joe Conway <mail@joeconway.com>
` Re: FW: Query execution failure
2023-09-28 01:00 UTC Bruce Momjian <bruce@momjian.us>
` Re: FW: Query execution failure
2023-09-28 01:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: FW: Query execution failure
2023-09-28 02:27 UTC Bruce Momjian <bruce@momjian.us>
` Re: FW: Query execution failure
2023-09-28 13:48 UTC Bruce Momjian <bruce@momjian.us>
` Re: FW: Query execution failure
2023-10-10 20:05 UTC Bruce Momjian <bruce@momjian.us>
[18+ messages in thread]
BUG #18153: Undefined Symbol creating postgis_raster extension
2023-10-10 12:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18153: Undefined Symbol creating postgis_raster extension
2023-10-10 15:20 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery
2023-09-05 05:31 UTC Lepikhov Andrei <lepikhov@fastmail.com>
` Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery
2023-09-11 06:28 UTC Richard Guo <guofenglinux@gmail.com>
` Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery
2023-09-11 09:03 UTC Lepikhov Andrei <lepikhov@fastmail.com>
` Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery
2023-09-14 04:58 UTC Lepikhov Andrei <lepikhov@fastmail.com>
` Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery
2023-09-28 06:32 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery
2023-10-09 08:41 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery
2023-10-10 14:01 UTC a.rybakina <a.rybakina@postgrespro.ru>
[7+ messages in thread]
pg_rewind: ERROR: could not fetch remote file "global/pg_control": ERROR: permission denied
2023-09-27 09:27 UTC Zhaoxun Yan <yan.zhaoxun@gmail.com>
` Re: pg_rewind: ERROR: could not fetch remote file "global/pg_control": ERROR: permission denied
2023-09-29 06:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_rewind: ERROR: could not fetch remote file "global/pg_control": ERROR: permission denied
2023-10-04 07:09 UTC Zhaoxun Yan <yan.zhaoxun@gmail.com>
` Re: pg_rewind: ERROR: could not fetch remote file "global/pg_control": ERROR: permission denied
2023-10-10 09:24 UTC Zhaoxun Yan <yan.zhaoxun@gmail.com>
[4+ messages in thread]
Access to old versions of a row
2023-10-08 15:25 UTC Matthias Apitz <guru@unixarea.de>
` Re: Access to old versions of a row
2023-10-08 19:35 UTC Vik Fearing <vik@postgresfriends.org>
` Re: Access to old versions of a row
2023-10-09 09:56 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Access to old versions of a row
2023-10-09 23:55 UTC Andres Freund <andres@anarazel.de>
[4+ messages in thread]
BUG #18151: pg_upgradecluster fails when column default refers to column
2023-10-08 17:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18151: pg_upgradecluster fails when column default refers to column
2023-10-09 14:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18151: pg_upgradecluster fails when column default refers to column
2023-10-09 14:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18151: pg_upgradecluster fails when column default refers to column
2023-10-09 15:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18151: pg_upgradecluster fails when column default refers to column
2023-10-09 16:13 UTC Liam Morland <liam@morland.ca>
` Re: BUG #18151: pg_upgradecluster fails when column default refers to column
2023-10-09 16:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #18150: The results returned by index only scan using gist index of bpchar and seqscan have difference.
2023-10-08 15:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18150: The results returned by index only scan using gist index of bpchar and seqscan have difference.
2023-10-08 16:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx
2023-10-08 13:16 UTC Hans Buschmann <buschmann@nidsa.net>
` Re: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx
2023-10-08 15:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18149: Incorrect lexeme for english token "proxy"
2023-10-05 21:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18149: Incorrect lexeme for english token "proxy"
2023-10-07 12:49 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18149: Incorrect lexeme for english token "proxy"
2023-10-07 14:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18149: Incorrect lexeme for english token "proxy"
2023-10-07 16:07 UTC Patrick Peralta <pperalta@gmail.com>
` Re: BUG #18149: Incorrect lexeme for english token "proxy"
2023-10-07 16:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18149: Incorrect lexeme for english token "proxy"
2023-10-07 18:22 UTC Patrick Peralta <pperalta@gmail.com>
[6+ messages in thread]
BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx
2023-10-05 14:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx
2023-10-05 15:12 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx
2023-10-05 17:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18148: Handle null in a date/time fields when passing empty arrays issue
2023-10-05 14:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18148: Handle null in a date/time fields when passing empty arrays issue
2023-10-05 15:07 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
REFRESH MATERIALIZED VIEW error
2023-10-04 17:46 UTC Given, Robert A <bgiven@bu.edu>
` Re: REFRESH MATERIALIZED VIEW error
2023-10-04 23:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: REFRESH MATERIALIZED VIEW error
2023-10-05 14:19 UTC Given, Robert A <bgiven@bu.edu>
[3+ messages in thread]
BUG ERROR: COULDN´T ACCESS THE URL
2023-10-03 16:45 UTC Priscilla Riggioni Leonhardes <riggioni83@gmail.com>
BUG #18144: While i am intalling postgresql-12 repo,i am facing the below.i tried with dowload and install.
2023-10-02 17:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18144: While i am intalling postgresql-12 repo,i am facing the below.i tried with dowload and install.
2023-10-03 13:40 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #18145: In psql, \d does not output in expanded format
2023-10-03 03:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18145: In psql, \d does not output in expanded format
2023-10-03 13:37 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #18142: strange behaviour of "UPDATE" with id_encode()
2023-10-02 08:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18142: strange behaviour of "UPDATE" with id_encode()
2023-10-02 14:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` BUG #18142: strange behaviour of "UPDATE" with id_encode()
2023-10-02 15:02 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18142: strange behaviour of "UPDATE" with id_encode()
2023-10-02 18:38 UTC DataSelfService Srl <info@dataselfservice.com>
[4+ messages in thread]
pg_restore 14 skips ACL COLUMN when --schema is used
2023-07-28 22:01 UTC Kong Man <kong_mansatiansin@hotmail.com>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-07-29 00:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-07-31 19:50 UTC Kong Man <kong_mansatiansin@hotmail.com>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-07-31 23:00 UTC Kong Man <kong_mansatiansin@hotmail.com>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-08-02 19:30 UTC Euler Taveira <euler@eulerto.com>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-08-02 20:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-08-02 20:53 UTC Euler Taveira <euler@eulerto.com>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-08-02 21:05 UTC Kong Man <kong_mansatiansin@hotmail.com>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-08-09 01:31 UTC Euler Taveira <euler@eulerto.com>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-08-09 13:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_restore 14 skips ACL COLUMN when --schema is used
2023-10-02 17:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
[11+ messages in thread]
BUG #18143: pg_upgrade fails to use port 50432 even with firewall disabled
2023-10-02 13:49 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18129: GiST index produces incorrect query results
2023-09-22 06:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18129: GiST index produces incorrect query results
2023-09-22 13:43 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18129: GiST index produces incorrect query results
2023-09-23 22:06 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18129: GiST index produces incorrect query results
2023-09-25 21:24 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18129: GiST index produces incorrect query results
2023-09-26 08:08 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18129: GiST index produces incorrect query results
2023-10-02 11:28 UTC Heikki Linnakangas <hlinnaka@iki.fi>
[6+ messages in thread]
BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-09-27 10:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-09-28 03:30 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-09-28 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-09-28 07:07 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-09-28 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-09-28 17:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-10-01 00:31 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-10-01 00:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-10-02 02:56 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
2023-10-02 03:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[10+ messages in thread]
BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
2023-09-26 01:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
2023-09-27 10:00 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
2023-09-30 06:36 UTC Jov <amutu@amutu.com>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
2023-09-30 23:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
2023-10-01 00:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
2023-10-01 00:54 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
2023-10-01 00:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
2023-10-02 02:27 UTC Michael Paquier <michael@paquier.xyz>
[8+ messages in thread]
BUG #18141: sorry, too many clients error occurring very frequently
2023-09-29 14:31 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #18141: sorry, too many clients error occurring very frequently
2023-09-29 18:12 UTC Wetmore, Matthew (CTR) <Matthew.Wetmore@express-scripts.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
2023-09-29 18:12 UTC Joe Conway <mail@joeconway.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
2023-09-30 18:04 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
2023-10-01 14:34 UTC Joe Conway <mail@joeconway.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
2023-10-01 18:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
2023-10-01 18:27 UTC Joe Conway <mail@joeconway.com>
` Re: BUG #18141: sorry, too many clients error occurring very frequently
2023-10-01 19:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
[8+ messages in thread]
Help pg_restore version
2023-09-30 10:33 UTC Jorge Soro Domenech <jorsodom@gmail.com>
` Re: Help pg_restore version
2023-10-01 13:29 UTC Euler Taveira <euler@eulerto.com>
` Re: Help pg_restore version
2023-10-01 15:28 UTC Jorge Soro Domenech <jorsodom@gmail.com>
` Re: Help pg_restore version
2023-10-01 15:34 UTC Jorge Soro Domenech <jorsodom@gmail.com>
` Re: Help pg_restore version
2023-10-01 16:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Help pg_restore version
2023-10-01 16:39 UTC Jorge Soro Domenech <jorsodom@gmail.com>
[6+ messages in thread]
Bug in postgresql related column level security authentication.
2023-10-01 07:59 UTC Shubham Gholap <shubhamgholap2910@gmail.com>
` Re: Bug in postgresql related column level security authentication.
2023-10-01 16:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
2023-09-28 07:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
2023-09-29 18:15 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
2023-09-29 18:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
2023-09-29 18:32 UTC Bruce Momjian <bruce@momjian.us>
[4+ 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