pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #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]
Broken type checking for empty subqueries
2023-09-28 09:08 UTC Marek Malevič <marek@malevicovi.net>
` Re: Broken type checking for empty subqueries
2023-09-28 11:28 UTC Vik Fearing <vik@postgresfriends.org>
` Re: Broken type checking for empty subqueries
2023-09-28 12:41 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Broken type checking for empty subqueries
2023-09-28 14:47 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Broken type checking for empty subqueries
2023-09-28 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Broken type checking for empty subqueries
2023-09-28 21:10 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Broken type checking for empty subqueries
2023-09-28 21:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Broken type checking for empty subqueries
2023-09-29 07:52 UTC David Rowley <dgrowleyml@gmail.com>
[8+ messages in thread]
md5 password valid and invalid after upgrading
2023-09-26 23:14 UTC Kyle MacMillan <macattackftw@gmail.com>
` Re: md5 password valid and invalid after upgrading
2023-09-27 08:04 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: md5 password valid and invalid after upgrading
2023-09-27 19:26 UTC Kyle MacMillan <macattackftw@gmail.com>
` Re: md5 password valid and invalid after upgrading
2023-09-27 22:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: md5 password valid and invalid after upgrading
2023-09-28 21:49 UTC Kyle MacMillan <macattackftw@gmail.com>
` Re: md5 password valid and invalid after upgrading
2023-09-28 22:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: md5 password valid and invalid after upgrading
2023-09-28 23:32 UTC Kyle MacMillan <macattackftw@gmail.com>
[7+ messages in thread]
BUG #18139: Causing FATAL error on database using function last() or first()
2023-09-28 17:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18139: Causing FATAL error on database using function last() or first()
2023-09-28 18:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18139: Causing FATAL error on database using function last() or first()
2023-09-28 19:36 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX CONCURRENTLY when blocksize=1
2023-09-21 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX CONCURRENTLY when blocksize=1
2023-09-22 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX CONCURRENTLY when blocksize=1
2023-09-28 07:16 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX CONCURRENTLY when blocksize=1
2023-09-28 16:25 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18127: Assertion HaveRegisteredOrActiveSnapshot failed on REINDEX CONCURRENTLY when blocksize=1
2023-09-28 16:31 UTC Andres Freund <andres@anarazel.de>
[5+ messages in thread]
BUG #18138: Using limit on VALUES causes type conversion to fail.
2023-09-28 12:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18138: Using limit on VALUES causes type conversion to fail.
2023-09-28 14:47 UTC Pantelis Theodosiou <ypercube@gmail.com>
` Re: BUG #18138: Using limit on VALUES causes type conversion to fail.
2023-09-28 15:04 UTC Akash Kava <ackava@gmail.com>
` Re: BUG #18138: Using limit on VALUES causes type conversion to fail.
2023-09-28 15:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Missed TidRangePath in the print_path switch
2023-09-28 05:07 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: Missed TidRangePath in the print_path switch
2023-09-28 10:33 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
回复： Bug of psql meta-command \sf & \sv
2023-09-28 02:09 UTC 咸�9�5 <2437705447@qq.com>
BUG #18136: lc_messages is the empty string but should be 'C'?
2023-09-27 15:04 UTC PG Bug reporting form <noreply@postgresql.org>
Bug of psql meta-command \sf & \sv
2023-09-27 09:06 UTC Jet Zhang <jet.cx.zhang@hotmail.com>
` Re: Bug of psql meta-command \sf & \sv
2023-09-27 09:13 UTC Daniel Gustafsson <daniel@yesql.se>
` RE: Bug of psql meta-command \sf & \sv
2023-09-27 09:25 UTC Jet Zhang <jet.cx.zhang@hotmail.com>
` Re: Bug of psql meta-command \sf & \sv
2023-09-27 10:33 UTC Japin Li <japinli@hotmail.com>
` RE: Bug of psql meta-command \sf & \sv
2023-09-27 11:03 UTC Jet Zhang <jet.cx.zhang@hotmail.com>
` Re: Bug of psql meta-command \sf & \sv
2023-09-27 12:35 UTC 咸�9�5 <2437705447@qq.com>
` Re: Bug of psql meta-command \sf & \sv
2023-09-27 14:16 UTC Japin Li <japinli@hotmail.com>
[7+ messages in thread]
PG_DUMPALL not executable within docker container
2023-09-27 08:43 UTC Patrick Frießnegg <patrick.fri@gmail.com>
` Re: PG_DUMPALL not executable within docker container
2023-09-27 09:06 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: PG_DUMPALL not executable within docker container
2023-09-27 09:47 UTC Patrick Frießnegg <patrick.fri@gmail.com>
[3+ messages in thread]
PostgreSQL's processes blocking each other are not detected as deadlock
2023-09-26 10:23 UTC Sorin Mircioiu <sorin.mircioiu@gmail.com>
` Re: PostgreSQL's processes blocking each other are not detected as deadlock
2023-09-26 14:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL's processes blocking each other are not detected as deadlock
2023-09-27 08:32 UTC Sorin Mircioiu <sorin.mircioiu@gmail.com>
[3+ messages in thread]
BUG #18103: bugs of concurrent merge into when use different join plan
2023-09-10 12:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
2023-09-14 07:29 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
2023-09-18 06:44 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
2023-09-21 11:49 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
2023-09-26 09:46 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18103: bugs of concurrent merge into when use different join plan
2023-09-27 07:29 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[6+ messages in thread]
BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
2023-09-21 06:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
2023-09-22 01:47 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
2023-09-22 01:55 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
2023-09-22 02:06 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
2023-09-22 02:07 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
2023-09-22 02:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
2023-09-25 17:45 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
2023-09-25 22:32 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
2023-09-26 16:09 UTC Bruce Momjian <bruce@momjian.us>
[9+ 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