pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19016: Re: BUG #18908: DEREF_OF_NULL: After having been assigned to a NULL value at descriptor.c:203
2025-08-08 07:09 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18908: DEREF_OF_NULL: After having been assigned to a NULL value at descriptor.c:203
2025-04-30 11:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18908: DEREF_OF_NULL: After having been assigned to a NULL value at descriptor.c:203
2025-05-08 12:55 UTC Robin Haberkorn <haberkorn@b1-systems.de>
` Re: BUG #18908: DEREF_OF_NULL: After having been assigned to a NULL value at descriptor.c:203
2025-08-08 07:08 UTC Алена Васильева <gorcom2012@gmail.com>
[3+ messages in thread]
BUG: IS NOT NULL on RECORD variable fails in 17.5-dev
2025-08-07 19:43 UTC Peter Praxmarer <ppraxmarer@gmail.com>
` Re: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev
2025-08-07 19:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev
2025-08-07 19:54 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev
2025-08-07 20:15 UTC Peter Praxmarer <ppraxmarer@gmail.com>
[4+ messages in thread]
BUG #19015: insert-returning failure: stable function in select policy doesn't see before-insert trigger change
2025-08-07 19:56 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-05 21:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-05 23:01 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 11:56 UTC dbman@sqlexec.com <dbman@sqlexec.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 14:53 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 15:42 UTC dbman@sqlexec.com <dbman@sqlexec.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 16:32 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 16:52 UTC dbman@sqlexec.com <dbman@sqlexec.com>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 18:04 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
2025-08-06 18:34 UTC David G. Johnston <david.g.johnston@gmail.com>
[9+ messages in thread]
BUG #16961: Could not access status of transaction
2021-04-13 15:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16961: Could not access status of transaction
2021-04-14 16:11 UTC Stepan Yankevych <stepya@ukr.net>
` RE: BUG #16961: Could not access status of transaction
2021-04-19 18:49 UTC Stepan Yankevych <Stepan_Yankevych@epam.com>
` Re: BUG #16961: Could not access status of transaction
2021-06-05 20:55 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #16961: Could not access status of transaction
2021-06-05 21:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16961: Could not access status of transaction
2021-06-05 21:31 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #16961: Could not access status of transaction
2025-06-25 04:04 UTC Daniil Davydov <3danissimo@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-01 03:41 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-01 03:50 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-04 11:08 UTC Daniil Davydov <3danissimo@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-05 23:30 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-06 03:30 UTC Daniil Davydov <3danissimo@gmail.com>
` Re: BUG #16961: Could not access status of transaction
2025-08-06 04:55 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
[13+ messages in thread]
CREATE DATABASE copies datlocale even if datlocprovider differs
2025-07-29 23:33 UTC Jeff Davis <pgsql@j-davis.com>
` Re: CREATE DATABASE copies datlocale even if datlocprovider differs
2025-08-05 16:28 UTC Jeff Davis <pgsql@j-davis.com>
[2+ messages in thread]
BUG #19008: Problems downloading metadata for dnf - probably missing private key (GPG signature)
2025-08-04 08:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19008: Problems downloading metadata for dnf - probably missing private key (GPG signature)
2025-08-05 14:40 UTC Álvaro Herrera <alvherre@kurilemu.de>
[2+ messages in thread]
AW: BUG #19011: repomd.xml.asc on postgresql 16 empty
2025-08-05 13:07 UTC Wehnert, Thomas <Thomas.Wehnert@uhb-software.com>
BUG #19012: GPG signature file for RHEL 9 is 0 bytes
2025-08-04 16:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19012: GPG signature file for RHEL 9 is 0 bytes
2025-08-05 12:57 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #19011: repomd.xml.asc on postgresql 16 empty
2025-08-04 15:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19011: repomd.xml.asc on postgresql 16 empty
2025-08-05 12:56 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
pgdg 16 package repo failure from missing repomd.xml.asc
2025-08-04 02:44 UTC Jeff Palmer <darren1713@gmail.com>
` Re: pgdg 16 package repo failure from missing repomd.xml.asc
2025-08-04 23:32 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #19010: Empty repomd.xml.asc file
2025-08-04 14:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19010: Empty repomd.xml.asc file
2025-08-04 23:31 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #19009: Empty repomd.xml.asc file on pgdg16 mirror causes metadata retrieval failure
2025-08-04 12:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19009: Empty repomd.xml.asc file on pgdg16 mirror causes metadata retrieval failure
2025-08-04 23:31 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-07-31 06:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-07-31 16:51 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-07-31 22:09 UTC Michael Paquier <michael@paquier.xyz>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 04:33 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 04:52 UTC Michael Paquier <michael@paquier.xyz>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 10:00 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 11:45 UTC Michael Paquier <michael@paquier.xyz>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 16:32 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-02 03:27 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-02 10:26 UTC Michael Paquier <michael@paquier.xyz>
[10+ messages in thread]
BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 12:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 19:53 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 20:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 21:20 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 22:48 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-25 16:06 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-22 02:27 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-24 16:30 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-24 21:06 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-25 14:15 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-28 21:15 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-28 21:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-30 19:13 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-08-01 22:01 UTC Nathan Bossart <nathandbossart@gmail.com>
[14+ messages in thread]
BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-27 05:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-28 02:23 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-28 06:38 UTC Stepan Neretin <slpmcf@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-28 08:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-31 05:30 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-31 15:43 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-31 18:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 02:38 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 03:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 04:38 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 04:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 19:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[12+ messages in thread]
BUG #19003: A SELECT that does not return a valid table
2025-07-30 19:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-30 21:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-30 21:38 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-31 09:17 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-31 10:50 UTC Alexandre Bailly <alexandrebailly1955@gmail.com>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-31 13:10 UTC Vik Fearing <vik@postgresfriends.org>
[6+ messages in thread]
BUG #19004: Incorrect lowercasing of word-final Greek capital Sigma (Σ)
2025-07-31 03:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19004: Incorrect lowercasing of word-final Greek capital Sigma (Σ)
2025-07-31 07:39 UTC John Naylor <johncnaylorls@gmail.com>
[2+ messages in thread]
BUG #15988: Improve ANALYZE-statement
2019-08-31 19:06 UTC PG Bug reporting form <noreply@postgresql.org>
` [PATCH v1 1/1] Allow ALTER SYSTEM to set unrecognized custom GUCs.
2025-07-30 18:34 UTC Nathan Bossart <nathan@postgresql.org>
` [PATCH v1 1/1] Allow ALTER SYSTEM to set unrecognized custom GUCs.
2025-07-30 18:34 UTC Nathan Bossart <nathan@postgresql.org>
[3+ messages in thread]
BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
2025-07-29 19:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
2025-07-29 19:54 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
2025-07-30 03:01 UTC Samuel Marks <samuelmarks@gmail.com>
` Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
2025-07-30 03:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins
2025-07-29 13:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins
2025-07-29 15:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins
2025-07-29 15:34 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[3+ messages in thread]
BUG #18987: psqlodbc_setup.exe installs as Unknown Publisher
2025-07-16 17:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18987: psqlodbc_setup.exe installs as Unknown Publisher
2025-07-28 11:51 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
Lower priority of the configure option --with-libraries causes wrong lib resolution
2025-06-15 16:20 UTC Charles Samborski <demurgos@demurgos.net>
` Re: Lower priority of the configure option --with-libraries causes wrong lib resolution
2025-06-15 20:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Lower priority of the configure option --with-libraries causes wrong lib resolution
2025-06-15 21:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Lower priority of the configure option --with-libraries causes wrong lib resolution
2025-07-27 22:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 04:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 13:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 14:40 UTC =?utf-8?B?SmluaHVpIExhaQ==?= <jinhui-lai@foxmail.com>
` Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 15:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 16:22 UTC David G. Johnston <david.g.johnston@gmail.com>
[5+ 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