pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #18061: The psql -v variable option does not work for the -c command option
  2023-08-18 14:28 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18061: The psql -v variable option does not work for the -c command option
  2023-08-20 16:58 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18061: The psql -v variable option does not work for the -c command option
  2023-08-22 15:31 UTC  Robert Greene <RobertMcCollisterGreene@hotmail.com>
  [3+ messages in thread]

BUG #18064: Order of cascading deletes by foreign key; "on delete restrict"
  2023-08-22 08:45 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18064: Order of cascading deletes by foreign key; "on delete restrict"
  2023-08-22 13:10 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

BUG #18063: postgresql-x64-14 service not working
  2023-08-22 07:11 UTC  PG Bug reporting form <noreply@postgresql.org>

Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
  2023-08-17 20:27 UTC  Emile Amewoto (ZA) <Emile.Amewoto@absa.africa>
` Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
  2023-08-18 05:36 UTC  Emile Amewoto <emileam@yahoo.com>
` Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
  2023-08-21 15:23 UTC  Euler Taveira <euler@eulerto.com>
` Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
  2023-08-21 16:20 UTC  Emile Amewoto <emileam@yahoo.com>
` Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
  2023-08-21 22:07 UTC  Michael Paquier <michael@paquier.xyz>
  [5+ messages in thread]

BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
  2010-01-13 19:10 UTC  Vincenzo Romano <vincenzo.romano@notorand.it>
` Re: BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
  2010-01-14 08:54 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
  2010-01-14 14:26 UTC  Vincenzo Romano <vincenzo.romano@notorand.it>
` Re: BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
  2010-01-14 14:36 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
  2010-01-14 14:59 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` PGRES_EMPTY_QUERY from Postgre 14.3
  2023-08-21 14:59 UTC  Sanjay Patil <sanjaypatilwork@gmail.com>
` Re: PGRES_EMPTY_QUERY from Postgre 14.3
  2023-08-21 15:52 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [7+ messages in thread]

BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
  2023-08-18 09:30 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
  2023-08-20 16:12 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
  2023-08-20 17:58 UTC  James Inform <james.inform@pharmapp.de>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
  2023-08-20 18:26 UTC  James Inform <james.inform@pharmapp.de>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
  2023-08-20 21:04 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
  2023-08-20 21:12 UTC  James Inform <james.inform@pharmapp.de>
  [6+ messages in thread]

BUG #18034: Accept the spelling "+infinity" in datetime input  is not accurate
  2023-07-20 15:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
  2023-08-10 02:39 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
  2023-08-10 02:53 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
  2023-08-10 11:25 UTC  Bruce Momjian <bruce@momjian.us>
` Re:Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
  2023-08-18 13:57 UTC  yanliang lei <msdnchina@163.com>
` Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
  2023-08-19 19:39 UTC  Vik Fearing <vik@postgresfriends.org>
  [6+ messages in thread]

BUG #18058: Http Extension Postgres
  2023-08-16 06:32 UTC  PG Bug reporting form <noreply@postgresql.org>

gpg error (again)
  2023-08-13 19:19 UTC  otheus uibk <otheus.uibk@gmail.com>
` Re: gpg error (again)
  2023-08-14 11:02 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

BUG #18054: Permission denied.
  2023-08-13 04:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18054: Permission denied.
  2023-08-14 03:00 UTC  Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #18054: Permission denied.
  2023-08-14 03:27 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #18013: Failed installing
  2023-07-03 08:41 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18013: Failed installing
  2023-08-13 19:15 UTC  otheus uibk <otheus.uibk@gmail.com>
` Re: BUG #18013: Failed installing
  2023-08-13 19:18 UTC  otheus uibk <otheus.uibk@gmail.com>
  [3+ messages in thread]

BUG #18040: PostgreSQL does not report its version correctly
  2023-07-27 21:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18040: PostgreSQL does not report its version correctly
  2023-08-11 02:02 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #18040: PostgreSQL does not report its version correctly
  2023-08-11 02:42 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18040: PostgreSQL does not report its version correctly
  2023-08-11 20:37 UTC  Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #18040: PostgreSQL does not report its version correctly
  2023-08-13 09:38 UTC  Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
  [5+ messages in thread]

BUG #18053: fastpath count per pid in pg_locks shows > 16 entries
  2023-08-10 12:31 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 08:55 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 12:57 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:04 UTC  Nicolas Gouteux <nicolas.gouteux@sonarsource.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:28 UTC  Nicolas Gouteux <nicolas.gouteux@sonarsource.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:37 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:43 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:47 UTC  Nicolas Gouteux <nicolas.gouteux@sonarsource.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:49 UTC  Nicolas Gouteux <nicolas.gouteux@sonarsource.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 15:02 UTC  Félix GERZAGUET <felix.gerzaguet@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 15:03 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 15:26 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [11+ messages in thread]

BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-25 12:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-25 14:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-26 06:49 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-26 08:05 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-27 11:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-28 06:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-28 07:02 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-29 02:22 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-29 09:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-29 10:39 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-30 04:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-30 05:59 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-08-02 18:01 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-08-08 00:31 UTC  Michael Paquier <michael@paquier.xyz>
  [14+ messages in thread]

search_path not recomputed when role name changes
  2023-07-27 18:21 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: search_path not recomputed when role name changes
  2023-07-30 04:08 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: search_path not recomputed when role name changes
  2023-07-30 05:58 UTC  Michael Paquier <michael@paquier.xyz>
` Re: search_path not recomputed when role name changes
  2023-08-02 19:09 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: search_path not recomputed when role name changes
  2023-08-03 23:28 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: search_path not recomputed when role name changes
  2023-08-07 23:20 UTC  Michael Paquier <michael@paquier.xyz>
  [6+ messages in thread]

BUG #18049: dynamic_shared_memory_type's value `posix` doesn't have any effect, syscall shm_get executes
  2023-08-04 05:22 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18049: dynamic_shared_memory_type's value `posix` doesn't have any effect, syscall shm_get executes
  2023-08-04 13:22 UTC  Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #18049: dynamic_shared_memory_type's value `posix` doesn't have any effect, syscall shm_get executes
  2023-08-07 14:38 UTC  jitu <jkr0103@gmail.com>
  [3+ messages in thread]

PostgreSQL doesn't display exact version
  2023-08-06 16:19 UTC  Jacob Pfundstein <jjpfst@gmail.com>

AW: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 14:53 UTC  [Quipsy] Markus Karg <karg@quipsy.de>
` AW: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-04 06:12 UTC  [Quipsy] Markus Karg <karg@quipsy.de>
  [2+ messages in thread]

BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 01:28 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 05:08 UTC  justin tocci <justin@tocci.org>
` Re: BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 05:14 UTC  Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 14:48 UTC  Justin Tocci <justin@wfprod.com>
` Re: BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 23:31 UTC  Thomas Munro <thomas.munro@gmail.com>
  [5+ messages in thread]

WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 14:20 UTC  [Quipsy] Markus Karg <karg@quipsy.de>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 14:48 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 14:53 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 15:02 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 17:55 UTC  Jaime Casanova <jcasanov@systemguards.com.ec>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 17:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [6+ messages in thread]

BUG #18048: Database process terminated automatically
  2023-08-03 10:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18048: Database process terminated automatically
  2023-08-03 11:42 UTC  David Rowley <dgrowleyml@gmail.com>
  [2+ messages in thread]

[BUG REPORT] Unexpected cast while matching CHAR type
  2023-08-02 17:23 UTC  翁思扬 <52275903002@stu.ecnu.edu.cn>
` Re: [BUG REPORT] Unexpected cast while matching CHAR type
  2023-08-02 18:35 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #18045: NpgSQL installation not working
  2023-08-01 14:37 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18045: NpgSQL installation not working
  2023-08-02 16:29 UTC  Euler Taveira <euler@eulerto.com>
  [2+ messages in thread]

pg_hba.conf "authentication file token too long, skipping"
  2023-07-24 15:05 UTC  Zechman, Derek S <Derek.S.Zechman@snapon.com>
` Re: pg_hba.conf "authentication file token too long, skipping"
  2023-07-24 16:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` RE: pg_hba.conf "authentication file token too long, skipping"
  2023-08-01 16:29 UTC  Zechman, Derek S <Derek.S.Zechman@snapon.com>
` Re: pg_hba.conf "authentication file token too long, skipping"
  2023-08-02 16:20 UTC  Euler Taveira <euler@eulerto.com>
  [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