pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedAttribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 09:48 UTC Duncan Sands <duncan.sands@deepbluecap.com>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 12:32 UTC Tender Wang <tndrwang@gmail.com>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 13:46 UTC Tender Wang <tndrwang@gmail.com>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 15:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 15:11 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 17:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 19:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 20:03 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 20:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-10 20:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-11 06:11 UTC Tender Wang <tndrwang@gmail.com>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-11 17:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-11 19:20 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-11 20:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-11 21:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-12 10:16 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-12 15:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-12 22:45 UTC Andres Freund <andres@anarazel.de>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-13 00:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-13 01:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-13 01:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-13 15:10 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: Attribute of type record has wrong type error with MERGE ... WHEN NOT MATCHED BY SOURCE THEN DELETE
2025-03-13 16:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
[23+ messages in thread]
BUG #18843: ERROR: Input of anonymous composite types is not implemented in array_agg function
2025-03-13 10:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18843: ERROR: Input of anonymous composite types is not implemented in array_agg function
2025-03-13 14:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-06 10:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-10 17:08 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 02:21 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 08:23 UTC Bruno Friedmann <bruno@ioda-net.ch>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 09:11 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 10:13 UTC Christoph Berg <myon@debian.org>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 10:58 UTC Bruno Friedmann <bruno@ioda-net.ch>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 11:03 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 12:36 UTC Bruno Friedmann <bruno@ioda-net.ch>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 12:44 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 17:25 UTC Andreas Rogge <andreas.rogge@bareos.com>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-11 17:36 UTC Andreas Rogge <andreas.rogge@bareos.com>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-12 14:32 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-12 14:55 UTC Andreas Rogge <andreas.rogge@bareos.com>
` Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides
2025-03-13 10:08 UTC Devrim Gündüz <devrim@gunduz.org>
[15+ messages in thread]
BUG #18842: Wrong state in pg_stat_replication?
2025-03-13 08:45 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-01 18:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-01 20:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-03 08:00 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-03 08:50 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-03 20:42 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-04 07:38 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-04 10:45 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-04 15:05 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-04 20:11 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-04 21:28 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-04 21:45 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-05 06:44 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-06 06:42 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-06 07:20 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-06 08:11 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-06 19:35 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-07 07:02 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-07 23:47 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-08 08:02 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-11 22:34 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-12 19:03 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-12 21:33 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-12 22:00 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-12 23:24 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-13 00:03 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
2025-03-13 08:14 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[26+ messages in thread]
BUG #18841: pgflex fails during build when Flex uses dynamic m4
2025-03-13 00:52 UTC PG Bug reporting form <noreply@postgresql.org>
Query result differences between PostgreSQL 17 vs 16
2025-02-21 16:13 UTC Ronald Cruz <cruz@rentec.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-21 23:05 UTC Bruce Momjian <bruce@momjian.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-21 23:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-22 01:01 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-22 02:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-22 03:08 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-26 06:14 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-26 06:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-26 07:03 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-26 08:46 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-27 04:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-28 08:47 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-28 15:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-02-28 22:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-03-03 06:40 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-03-03 06:50 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-03-03 15:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-03-04 07:30 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-03-11 22:03 UTC Bruce Momjian <bruce@momjian.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-03-11 22:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-03-11 22:58 UTC Bruce Momjian <bruce@momjian.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-03-12 00:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query result differences between PostgreSQL 17 vs 16
2025-03-12 01:56 UTC Bruce Momjian <bruce@momjian.us>
[23+ messages in thread]
Unqualified name not resolved in function called from materialized view (17.4)
2025-03-11 08:45 UTC Peter Wright <pete@flooble.net>
` Re: Unqualified name not resolved in function called from materialized view (17.4)
2025-03-11 11:58 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unqualified name not resolved in function called from materialized view (17.4)
2025-03-11 21:54 UTC Peter Wright <pete@flooble.net>
[3+ messages in thread]
Datatype mismatch warning in logical replication when creating subscription
2025-03-11 15:02 UTC BharatDB <bharatdbpg@gmail.com>
BRIN index creation on geometry column causes crash
2025-01-02 22:02 UTC Tobias Wendorff <tobias.wendorff@tu-dortmund.de>
` Re: BRIN index creation on geometry column causes crash
2025-01-03 00:15 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BRIN index creation on geometry column causes crash
2025-01-03 00:25 UTC Tomas Vondra <tomas@vondra.me>
` Re: BRIN index creation on geometry column causes crash
2025-02-12 10:55 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BRIN index creation on geometry column causes crash
2025-02-12 18:12 UTC Tomas Vondra <tomas@vondra.me>
` Re: BRIN index creation on geometry column causes crash
2025-03-11 11:56 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
[6+ messages in thread]
BUG #18838: Missing characters in replication slot when bytea_output is set to "escape"
2025-03-10 13:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18838: Missing characters in replication slot when bytea_output is set to "escape"
2025-03-10 20:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-07 06:02 UTC Christopher Inokuchi <cinokuchi@gmail.com>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-07 14:23 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-07 20:53 UTC Christopher Inokuchi <cinokuchi@gmail.com>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-08 00:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-08 00:30 UTC Christopher Inokuchi <cinokuchi@gmail.com>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-08 03:17 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-08 19:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-09 01:07 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-09 17:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-09 19:48 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Window Functions with identical PARTITION BY and ORDER BY clauses evaluated separately
2025-03-10 14:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
[11+ messages in thread]
BUG #18837: YUM Repo URL throws HTTP 404
2025-03-10 10:53 UTC PG Bug reporting form <noreply@postgresql.org>
Memoize in between of two JOIN nodes
2025-03-06 11:17 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Memoize in between of two JOIN nodes
2025-03-07 01:13 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Memoize in between of two JOIN nodes
2025-03-10 09:22 UTC Andrei Lepikhov <lepihov@gmail.com>
[3+ messages in thread]
Error from array_agg when table has many rows
2025-03-07 20:07 UTC Kirill Zdornyy <kirill@dineserve.com>
` Re: Error from array_agg when table has many rows
2025-03-08 09:38 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Error from array_agg when table has many rows
2025-03-08 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error from array_agg when table has many rows
2025-03-09 07:22 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error from array_agg when table has many rows
2025-03-09 17:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
Is it possible for a WAL file to be missing records?
2025-03-09 07:55 UTC 와따가따 <lght2000@gmail.com>
BUG #18836: Cannot import foreign schema under different schema name when foreign table uses row types
2025-03-07 21:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18836: Cannot import foreign schema under different schema name when foreign table uses row types
2025-03-08 01:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18836: Cannot import foreign schema under different schema name when foreign table uses row types
2025-03-08 19:32 UTC Marcin Wisnicki <mwisnicki@gmail.com>
[3+ messages in thread]
BUG #18834: Query planer is choosing the sub-optimal plan when limit is present
2025-03-07 16:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18834: Query planer is choosing the sub-optimal plan when limit is present
2025-03-07 23:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18835: spgist index fails to accept point with NaN
2025-03-07 18:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18835: spgist index fails to accept point with NaN
2025-03-07 20:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18825: Row value equality predicates do not use indices
2025-02-25 22:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18825: Row value equality predicates do not use indices
2025-02-26 00:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18825: Row value equality predicates do not use indices
2025-03-06 16:50 UTC Nico Williams <nico@cryptonector.com>
[3+ messages in thread]
BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-03 09:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-03 10:10 UTC Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-03 11:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-04 08:18 UTC Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-04 08:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-04 18:12 UTC Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-04 23:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-10 09:08 UTC Haribabu Kommi <kommi.haribabu@gmail.com>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-10 09:53 UTC Haribabu Kommi <kommi.haribabu@gmail.com>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-10 12:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows
2019-07-10 15:43 UTC Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
` [PATCH v2 2/2] Remove obsolete comment in SnapBuildRestoreSnapshot()
2025-03-04 07:12 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` [PATCH v3 2/2] Remove obsolete comment in SnapBuildRestoreSnapshot()
2025-03-04 07:12 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
[13+ messages in thread]
BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-03 08:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-04 04:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-09 20:15 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-09 21:46 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-10 04:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-10 07:55 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-10 15:24 UTC Magnus Hagander <magnus@hagander.net>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-10 23:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-11 11:21 UTC Magnus Hagander <magnus@hagander.net>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-11 13:09 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-11 13:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15888: Bogus "idle in transaction" state for logical decoding client after creating a slot
2019-07-12 01:25 UTC Michael Paquier <michael@paquier.xyz>
` [PATCH v4] Fix bug in pg_logicalinspect functions
2025-03-04 05:43 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` [PATCH v5] Fix bug in pg_logicalinspect functions
2025-03-04 05:43 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` [PATCH v6] Fix bug in pg_logicalinspect functions
2025-03-04 05:43 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` [PATCH v7] Fix bug in pg_logicalinspect functions
2025-03-04 05:43 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` [PATCH v3 1/2] Fix bug in pg_logicalinspect functions
2025-03-04 05:43 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` [PATCH v2 1/2] Fix bug in pg_logicalinspect functions
2025-03-04 05:43 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
[18+ messages in thread]
BUG #18829: RAISE NOTICE appends 's' to string in PostgreSQL 17.2
2025-03-02 14:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18829: RAISE NOTICE appends 's' to string in PostgreSQL 17.2
2025-03-02 16:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18829: RAISE NOTICE appends 's' to string in PostgreSQL 17.2
2025-03-02 16:10 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #18829: RAISE NOTICE appends 's' to string in PostgreSQL 17.2
2025-03-02 18:59 UTC Robert Treat <rob@xzilla.net>
[4+ messages in thread]
BUG #18819: Error installing Postgresql
2025-02-18 17:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18819: Error installing Postgresql
2025-02-19 07:55 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: BUG #18819: Error installing Postgresql
2025-03-01 11:20 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[3+ messages in thread]
BUG #18827: PostgreSQL 17.4-1 Installation – Database Cluster Initialization Failed Due to Execution Policy
2025-02-27 19:08 UTC PG Bug reporting form <noreply@postgresql.org>
[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