pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19352: SQL Error messages do not include schema name along with table or data object name.
2025-12-12 02:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name.
2025-12-12 09:00 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name.
2025-12-12 15:10 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name.
2025-12-12 15:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Bug in sub-query
2025-12-12 10:59 UTC Veeranjaneya Vara Prasad Peddireddy <varaprasad.peddireddy@valuelabs.com>
` Re: Bug in sub-query
2025-12-12 15:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19339: odbc_fdw extension, Not able to read data from foreign tables
2025-12-01 20:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19339: odbc_fdw extension, Not able to read data from foreign tables
2025-12-10 11:41 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #19339: odbc_fdw extension, Not able to read data from foreign tables
2025-12-10 15:50 UTC Vijay Reddy <vijay.reddy@programming.com>
` Re: BUG #19339: odbc_fdw extension, Not able to read data from foreign tables
2025-12-11 11:01 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
[4+ messages in thread]
BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 10:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 16:24 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 16:31 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 16:36 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 17:18 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 17:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 17:29 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 17:45 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 17:51 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 20:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-02 21:44 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-03 07:51 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-03 15:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-04 17:14 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-06 01:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation
2025-12-10 10:03 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[16+ messages in thread]
BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-08-03 16:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-08-03 17:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-08-04 04:28 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-08-04 09:14 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-08-04 09:24 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-08-20 09:37 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-08-22 07:25 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-09-01 06:00 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-09-26 09:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19007: Planner fails to choose partial index with spurious 'not null'
2025-12-10 02:11 UTC Richard Guo <guofenglinux@gmail.com>
[10+ messages in thread]
BUG #19348: Disk space error when running COPY after upgrading to PostgreSQL 17.7
2025-12-09 11:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19348: Disk space error when running COPY after upgrading to PostgreSQL 17.7
2025-12-09 14:28 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #19348: Disk space error when running COPY after upgrading to PostgreSQL 17.7
2025-12-09 21:19 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19348: Disk space error when running COPY after upgrading to PostgreSQL 17.7
2025-12-10 01:07 UTC weijie JL <weijie1006jl@gmail.com>
[4+ messages in thread]
BUG #19345: MemoryContextSizeFailure after upgrade 14.11 to 17.7 in stored procedure
2025-12-05 02:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19345: MemoryContextSizeFailure after upgrade 14.11 to 17.7 in stored procedure
2025-12-05 13:36 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19345: MemoryContextSizeFailure after upgrade 14.11 to 17.7 in stored procedure
2025-12-06 21:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19345: MemoryContextSizeFailure after upgrade 14.11 to 17.7 in stored procedure
2025-12-09 11:30 UTC weijie JL <weijie1006jl@gmail.com>
[4+ messages in thread]
BUG #19340: Wrong result from CORR() function
2025-12-02 07:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-02 11:30 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-02 14:05 UTC Oleg Ivanov <o15611@gmail.com>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-02 17:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-02 17:22 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-02 18:54 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-02 20:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-02 23:03 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-02 23:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-02 23:48 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-03 00:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-03 01:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-03 11:38 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-03 16:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-03 22:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-04 00:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-05 09:23 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-05 10:17 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-05 22:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-06 06:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-06 11:51 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-06 18:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-06 22:53 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19340: Wrong result from CORR() function
2025-12-06 23:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
[24+ messages in thread]
Segfault due to NULL ParamExecData value
2025-12-04 14:25 UTC Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
` Re: Segfault due to NULL ParamExecData value
2025-12-04 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Segfault due to NULL ParamExecData value
2025-12-05 13:33 UTC Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
[3+ messages in thread]
Re：GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-05 02:17 UTC Haowu Ge <gehaowu@bitmoe.com>
BUG #19343: toast_internals.c:139:2: warning: missing braces around initializer [-Wmissing-braces]
2025-12-02 19:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19343: toast_internals.c:139:2: warning: missing braces around initializer [-Wmissing-braces]
2025-12-03 09:13 UTC Heikki Linnakangas <hlinnaka@iki.fi>
[2+ messages in thread]
BUG #19342: ERROR: function gcd(smallint, smallint) is not unique
2025-12-02 13:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19342: ERROR: function gcd(smallint, smallint) is not unique
2025-12-02 13:36 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
BUG #19338: [PG15] Unstable SQL result in test regress/tablespace
2025-12-01 11:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19338: [PG15] Unstable SQL result in test regress/tablespace
2025-12-01 15:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19338: [PG15] Unstable SQL result in test regress/tablespace
2025-12-01 16:52 UTC Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
[3+ messages in thread]
BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
2025-11-27 08:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
2025-11-27 16:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
2025-11-27 17:51 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
2025-11-28 09:26 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
2025-11-28 09:56 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
2025-11-28 11:07 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
2025-11-28 18:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
2025-11-28 18:36 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
2025-12-01 09:03 UTC Daniel Gustafsson <daniel@yesql.se>
[9+ messages in thread]
BUG #19337: Errors during downloading metadata for repository pgdg-rhel9-extras
2025-11-28 21:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19337: Errors during downloading metadata for repository pgdg-rhel9-extras
2025-11-30 20:50 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
Segmentation fault in var_is_nonnullable when running query with COUNT() on 42473b3b
2025-11-29 09:12 UTC Birler, Altan <altan.birler@tum.de>
` Re: Segmentation fault in var_is_nonnullable when running query with COUNT() on 42473b3b
2025-11-29 19:43 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segmentation fault in var_is_nonnullable when running query with COUNT() on 42473b3b
2025-11-29 23:56 UTC David Rowley <dgrowleyml@gmail.com>
[3+ messages in thread]
BUG #19336: TRAP: failed Assert("!IsTransactionOrTransactionBlock()")
2025-11-27 10:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19336: TRAP: failed Assert("!IsTransactionOrTransactionBlock()")
2025-11-27 15:55 UTC Álvaro Herrera <alvherre@kurilemu.de>
[2+ messages in thread]
BUG #19334: Cannot download packages from the mirrors
2025-11-24 19:49 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19333: 404s when accessing items from https://ftp.postgresql.org/pub/repos/yum/17/redhat/rhel-10-aarch64/
2025-11-24 19:18 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump
2025-11-10 15:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump
2025-11-11 01:11 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump
2025-11-11 01:42 UTC Haiyang Li <mohen.lhy@alibaba-inc.com>
` Re: BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump
2025-11-11 02:12 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump
2025-11-11 02:46 UTC Haiyang Li <mohen.lhy@alibaba-inc.com>
` Re: BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump
2025-11-12 06:35 UTC Haiyang Li <mohen.lhy@alibaba-inc.com>
` Re: BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump
2025-11-17 01:34 UTC ocean_li_996 <ocean_li_996@163.com>
` Re: BUG #19109: catalog lookup with the wrong snapshot duringlogical decoding causes coredump
2025-11-19 03:23 UTC =?utf-8?B?Y2NhNTUwNw==?= <cca5507@qq.com>
` Re: BUG #19109: catalog lookup with the wrong snapshot duringlogical decoding causes coredump
2025-11-20 18:16 UTC ocean_li_996 <ocean_li_996@163.com>
` Re: BUG #19109: catalog lookup with the wrong snapshotduringlogical decoding causes coredump
2025-11-21 03:21 UTC =?utf-8?B?Y2NhNTUwNw==?= <cca5507@qq.com>
` Re: BUG #19109: catalog lookup with the wrong snapshotduringlogical decoding causes coredump
2025-11-21 08:37 UTC =?utf-8?B?Y2NhNTUwNw==?= <cca5507@qq.com>
[11+ messages in thread]
BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
2025-11-17 06:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
2025-11-17 07:50 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: [EXTERNAL] Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
2025-11-19 09:54 UTC S, Naveen Krishna (Development Engineer 3) <naveenkrishna.s@sky.uk>
` Re: [EXTERNAL] Re: BUG #19114: ORDER BY ASC is tampering result when calculating distance btw vectors
2025-11-19 20:22 UTC Thomas Munro <thomas.munro@gmail.com>
[4+ messages in thread]
pg_resetwal prints new OldestXID in wrong circumstances
2025-11-19 09:52 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: pg_resetwal prints new OldestXID in wrong circumstances
2025-11-19 10:05 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: pg_resetwal prints new OldestXID in wrong circumstances
2025-11-19 16:08 UTC Heikki Linnakangas <hlinnaka@iki.fi>
[3+ messages in thread]
AW: BUG #19113: Missing updated libpq5 rpm in repo pgdg-common after minor release to 18.1
2025-11-19 11:44 UTC Hans Buschmann <buschmann@nidsa.net>
BUG #19119: Linux 6.14.0-1015-aws #15~24.04.1-Ubuntu SMP aarch64 aarch64 aarch64 GNU/Linux
2025-11-18 22:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19119: Linux 6.14.0-1015-aws #15~24.04.1-Ubuntu SMP aarch64 aarch64 aarch64 GNU/Linux
2025-11-19 06:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19113: Missing updated libpq5 rpm in repo pgdg-common after minor release to 18.1
2025-11-15 12:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19113: Missing updated libpq5 rpm in repo pgdg-common after minor release to 18.1
2025-11-18 21:02 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ 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