pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedLost update in an ordered batch, but only with index scan
2025-12-28 23:07 UTC Bernice Southey <bernice.southey@gmail.com>
` Re: Lost update in an ordered batch, but only with index scan
2025-12-29 08:12 UTC Richard Guo <guofenglinux@gmail.com>
[2+ messages in thread]
Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 02:19 UTC Alexey Makhmutov <a.makhmutov@postgrespro.ru>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 09:48 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 10:33 UTC shveta malik <shveta.malik@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 13:29 UTC Alexey Makhmutov <a.makhmutov@postgrespro.ru>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 15:31 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 18:22 UTC Alexey Makhmutov <a.makhmutov@postgrespro.ru>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 23:47 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-28 07:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-28 16:12 UTC Alexey Makhmutov <a.makhmutov@postgrespro.ru>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-29 07:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-29 10:28 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-29 23:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-06-02 03:17 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-12-26 11:14 UTC G. Sl <skokoveshat@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-12-29 00:09 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-12-29 05:22 UTC G. Sl <skokoveshat@gmail.com>
[16+ messages in thread]
BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
2025-12-26 15:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
2025-12-27 05:12 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
2025-12-27 17:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
2025-12-27 21:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan
2025-12-16 03:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan
2025-12-26 06:59 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan
2025-12-26 07:20 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan
2025-12-26 07:59 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
[4+ messages in thread]
Regression: partial index with IS NOT NULL predicate not used for min/max optimization on NOT NULL columns
2025-12-24 16:46 UTC Dmytro Astapov <dastapov@gmail.com>
` Re: Regression: partial index with IS NOT NULL predicate not used for min/max optimization on NOT NULL columns
2025-12-24 17:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Regression: partial index with IS NOT NULL predicate not used for min/max optimization on NOT NULL columns
2025-12-24 18:43 UTC Dmytro Astapov <dastapov@gmail.com>
[3+ messages in thread]
BUG #19359: Row level security: Upserts require insert policies in the update path
2025-12-18 15:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19359: Row level security: Upserts require insert policies in the update path
2025-12-19 17:40 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19359: Row level security: Upserts require insert policies in the update path
2025-12-19 23:12 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[3+ messages in thread]
[BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC)
2025-12-18 06:42 UTC =?utf-8?B?56ysMTA45qyh5piO5aSp?= <87326549@qq.com>
` Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC)
2025-12-18 08:40 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC)
2025-12-18 13:30 UTC Greg Sabino Mullane <htamfids@gmail.com>
[3+ messages in thread]
BUG #19358: Short circuit optimization exists in generic plan but missed in custom plan
2025-12-17 12:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19358: Short circuit optimization exists in generic plan but missed in custom plan
2025-12-17 21:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query.
2025-12-17 06:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query.
2025-12-17 14:54 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #19357: PostgreSQL generates a custom plan that performsworse than the generic plan for a certain query.
2025-12-17 15:17 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query.
2025-12-17 15:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query.
2025-12-17 15:52 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19357: PostgreSQL generates a custom plan that performsworse than the generic plan for a certain query.
2025-12-17 15:53 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #19357: PostgreSQL generates a custom plan that performsworsethan the generic plan for a certain query.
2025-12-17 16:08 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19357: PostgreSQL generates a custom plan that performsworsethan the generic plan for a certain query.
2025-12-17 16:15 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #19357: PostgreSQL generates a custom plan thatperformsworsethan the generic plan for a certain query.
2025-12-17 16:20 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19357: PostgreSQL generates a custom plan thatperformsworsethan the generic plan for a certain query.
2025-12-17 16:33 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #19357: PostgreSQL generates a custom plan that performsworsethan the generic plan for a certain query.
2025-12-17 17:11 UTC Greg Sabino Mullane <htamfids@gmail.com>
[11+ messages in thread]
BUG #19350: Short circuit optimization missed when running sql scriptes in JDBC
2025-12-10 10:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19350: Short circuit optimization missed when running sql scriptes in JDBC
2025-12-10 13:33 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC
2025-12-10 13:41 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19350: Short circuit optimization missed when running sql scriptes in JDBC
2025-12-10 13:46 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC
2025-12-10 14:01 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC
2025-12-10 16:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC
2025-12-16 15:17 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC
2025-12-17 01:40 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC
2025-12-17 12:55 UTC Dave Cramer <davecramer@postgres.rocks>
` Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC
2025-12-17 14:51 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC
2025-12-17 15:33 UTC Dave Cramer <davecramer@postgres.rocks>
` Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC
2025-12-17 15:39 UTC Dave Cramer <davecramer@postgres.rocks>
` Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC
2025-12-17 15:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
[13+ messages in thread]
Possible performance issues: DISTINCT ON + ORDER BY and JIT with aggregation
2025-12-17 00:25 UTC Jhonathan Cruz <jhonathancruz48@gmail.com>
` Re: Possible performance issues: DISTINCT ON + ORDER BY and JIT with aggregation
2025-12-17 15:14 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
Cluster is not being created
2025-12-13 19:34 UTC T iv <tiv060370@gmail.com>
` Re: Cluster is not being created
2025-12-15 16:50 UTC Robert Haas <robertmhaas@gmail.com>
` Re: Cluster is not being created
2025-12-17 05:32 UTC VASUKI M <vasukianand0119@gmail.com>
[3+ messages in thread]
BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs
2025-11-23 08:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs
2025-11-23 11:39 UTC Sergey Naumov <sknaumov@gmail.com>
` Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs
2025-11-23 22:06 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs
2025-12-04 10:19 UTC Sergey Naumov <sknaumov@gmail.com>
` Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs
2025-12-10 03:46 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs
2025-12-10 10:33 UTC Sergey Naumov <sknaumov@gmail.com>
` Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs
2025-12-15 19:35 UTC David Rowley <dgrowleyml@gmail.com>
[7+ messages in thread]
recovery_target discrepancy?
2025-12-13 12:18 UTC Thomas Rosenstein <thomas@thoro.at>
BUG #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]
[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