Архив рассылок [pgsql-bugs]
- Re: BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always Tom Lane
 - BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL PG Bug reporting form
 
- Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
 - BUG #18944: Assertion Failure in psql with idle_session_timeout Set PG Bug reporting form
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Duncan Sands
 - RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
 - BUG #18945: Standby synchronization problem PG Bug reporting form
 - Re: BUG #18945: Standby synchronization problem Dilip Kumar
 - function 'IS JSON ARRAY' not identified Badia, Antonio
 - Re: function 'IS JSON ARRAY' not identified Tom Lane
 - Re: function 'IS JSON ARRAY' not identified Badia, Antonio
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set Anthonin Bonnefoy
 - Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 Nathan Bossart
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 Rahila Syed
 - Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 Matheus Alcantara
 
- Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set Michael Paquier
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
 - Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 Michael Paquier
 - BUG #18946: Installation Setup File PG Bug reporting form
 - Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set Anthonin Bonnefoy
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
 - Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 Matheus Alcantara
 - Re: BUG #18946: Installation Setup File Sandeep Thakkar
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Tom Lane
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 
- Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 Michael Paquier
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
 - Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 Peter Eisentraut
 - Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 Matheus Alcantara
 - Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 Matheus Alcantara
 - Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw Thomas Munro
 - Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw Joseph Ayers
 - Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw Andres Freund
 
- Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Michael Paquier
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
 - RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Jim Jones
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
 - RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
 - RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Jim Jones
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 
- Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw Joseph Ayers
 - Function Error Response Is Not Clear Luke Muther
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Michael Paquier
 - RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
 - BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements PG Bug reporting form
 - RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Jim Jones
 - Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw Thomas Munro
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 
- BUG #18948: Equivalent MAX() result in view and inline query yields inconsistent row count PG Bug reporting form
 - Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq BATBAATAR Dorjpalam
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
 - BUG #18949: 分区表创建主键或者唯一约束需要有分区键 PG Bug reporting form
 - Re: BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw Thomas Munro
 - Re: BUG #18949: 分区表创建主键或者唯一约束需要有分区键 Dilip Kumar
 - Re: Function Error Response Is Not Clear Tom Lane
 - BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 PG Bug reporting form
 - Re: BUG #18948: Equivalent MAX() result in view and inline query yields inconsistent row count Tom Lane
 - Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Dilip Kumar
 
- Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Laurenz Albe
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Michael Paquier
 - Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Michael Paquier
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Jim Jones
 - Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Dilip Kumar
 - tlsv1 alert iso-8859-1 ca error on cert authentication Andrus
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
 - BUG #18951: Precision loss in inner join while using SUM aggregate function PG Bug reporting form
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Tom Lane
 - Re: BUG #18951: Precision loss in inner join while using SUM aggregate function Junwang Zhao
 - Re: BUG #18951: Precision loss in inner join while using SUM aggregate function Tom Lane
 - Re: tlsv1 alert iso-8859-1 ca error on cert authentication Tom Lane
 - Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Jim Jones
 
- Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Michael Paquier
 - Re: tlsv1 alert iso-8859-1 ca error on cert authentication Andrus
 - Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Fujii Masao
 - Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 Braulio Fdo Gonzalez
 - Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq Tom Lane
 - Re: tlsv1 alert iso-8859-1 ca error on cert authentication Jacob Champion
 - Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq Tom Lane
 - Re: tlsv1 alert iso-8859-1 ca error on cert authentication Andrus
 
- Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq Tom Lane
 - RE: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 Hayato Kuroda (Fujitsu)
 - Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Michael Paquier
 - BUG #18952: pg_restore --help and document have strange description: Dump something PG Bug reporting form
 - Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction" Andrei Varashen
 - Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction" Laurenz Albe
 - BUG #18953: Planner fails to build plan for complex query with LATERAL references PG Bug reporting form
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 
- Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Michael Paquier
 - Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Fujii Masao
 - RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
 - Re: BUG #18952: pg_restore --help and document have strange description: Dump something TAKATSUKA Haruka
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
 - Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set Никита Калинин
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo
 - BUG #18954: Error "could not reserve shared memory region ... error code 487" on Windows PG Bug reporting form
 - BUG #18955: pg_ctl output not being logged in stderr log on Windows if started with "net start" PG Bug reporting form
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo
 - Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set Anthonin Bonnefoy
 - Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build Soumyadeep Chakraborty
 
- Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build Nathan Bossart
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Michael Paquier
 - Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build John Naylor
 - BUG #18956: Observing an issue in regexp_count() PG Bug reporting form
 - Re: BUG #18956: Observing an issue in regexp_count() hubert depesz lubaczewski
 - Re: BUG #18952: pg_restore --help and document have strange description: Dump something Fujii Masao
 - Re: BUG #18952: pg_restore --help and document have strange description: Dump something Daniel Gustafsson
 - Re: BUG #18956: Observing an issue in regexp_count() Tom Lane
 - Re: BUG #18956: Observing an issue in regexp_count() hubert depesz lubaczewski
 - Re: BUG #18952: pg_restore --help and document have strange description: Dump something Fujii Masao
 - Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build Soumyadeep Chakraborty
 
- Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane
 - BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows PG Bug reporting form
 - Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows David G. Johnston
 - BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. PG Bug reporting form
 - Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows Seva Zaslavsky
 - Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows David G. Johnston
 - Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows Seva Zaslavsky
 - Re: BUG #18958: "pg_ctl start" allows subsequent CTRL-C key in cmd.exe to unexpectedly terminate cluster on Windows David G. Johnston
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane
 
- Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane
 
- Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought
 - Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane
 - Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build Andy Fan
 - Lower priority of the configure option --with-libraries causes wrong lib resolution Charles Samborski
 - Re: Lower priority of the configure option --with-libraries causes wrong lib resolution Tom Lane
 
- Re: Lower priority of the configure option --with-libraries causes wrong lib resolution Tom Lane
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
 - Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build John Naylor
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane
 
- Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9 Masahiko Sawada
 - Re: [E] Re: BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672" Masahiko Sawada
 - Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 Masahiko Sawada
 - Re: BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9 Laurence Parry
 
- Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Anthonin Bonnefoy
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Dilip Kumar
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Phineas Jensen
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Tom Lane
 - PostgreSQL 17 Service Running but Not Listening on Network Port on Windows José António Gomes
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Tom Lane
 - BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) PG Bug reporting form
 - Re: PostgreSQL 17 Service Running but Not Listening on Network Port on Windows David G. Johnston
 - Re: PostgreSQL 17 Service Running but Not Listening on Network Port on Windows Tom Lane
 
- Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) Tom Lane
 - BUG #18961: Race scenario where max_standby_streaming_delay is not honored PG Bug reporting form
 - Re: "unexpected duplicate for tablespace" problem in logical replication Ashutosh Bapat
 - BUG #18962: Type Conversion incorrect when performing UNION of queries. PG Bug reporting form
 - AW: [EXTERNAL] Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Chrzan, Maximilian
 - Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Dilip Kumar
 - Re: [EXTERNAL] Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Dilip Kumar
 - Re: BUG #18962: Type Conversion incorrect when performing UNION of queries. Tom Lane
 - BUG #18962: Type Conversion incorrect when performing UNION of queries. David G. Johnston
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Junwang Zhao
 - Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Anthony Hsu
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Dilip Kumar
 - BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint PG Bug reporting form
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Tom Lane
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Tom Lane
 
- Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Alexander Lakhin
 - Re: BUG #18962: Type Conversion incorrect when performing UNION of queries. Sundar Mudupalli
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Duncan Sands
 - RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Dilip Kumar
 - BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist PG Bug reporting form
 - Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint Tom Lane
 - BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions PG Bug reporting form
 - Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Tom Lane
 - Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions David G. Johnston
 - Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions Tom Lane
 - Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Nathan Bossart
 - Index Rebuild Bug fixed in 14.6.7 Kumar Boinpalli
 - Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Tom Lane
 - Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint Mathias Panzenböck
 - Re: Index Rebuild Bug fixed in 14.6.7 Bruce Momjian
 
- Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Nathan Bossart
 - Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Nathan Bossart
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) Tom Lane
 - Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) Dmitry Kovalenko
 
- Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) Tom Lane
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Alexander Lakhin
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane
 
- Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo
 - RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane
 
- Re: BUG #18509: Logical decoding behaves badly when processing a change record for a table with altered column Ajin Cherian
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Tom Lane
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
 - Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Tom Lane
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Alexander Lakhin
 - BUG #18966: Invalid SQL queries hang indefinitely until server restart PG Bug reporting form
 - Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart Tom Lane
 
- BUG #18968: GiST Index Cost Estimation PG Bug reporting form
 - Re: BUG #16961: Could not access status of transaction Daniil Davydov
 - Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart Laurenz Albe
 - BUG #18969: security tests failures PG Bug reporting form
 - Re: BUG #18969: security tests failures Daniel Gustafsson
 - Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart Jérémy Spriet
 - Re: PGXS does not properly uninstall documentation Karl O. Pinc
 - Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Nathan Bossart
 
- Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Dilip Kumar
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo
 - Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Anthony Hsu
 - Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Dilip Kumar
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane
 
- Re: BUG #18968: GiST Index Cost Estimation Tom Lane
 - Re: PGXS does not properly uninstall documentation Tom Lane
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Alexander Lakhin
 - BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure PG Bug reporting form
 - BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program PG Bug reporting form
 - Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane
 - Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program Tom Lane
 - Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program Dmitry Kovalenko
 - Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program Tom Lane
 
- Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program David G. Johnston
 - Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 Braulio Fdo Gonzalez
 - Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure jian he
 - Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program Laurenz Albe
 - Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane
 - Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane
 
- Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure jian he
 - Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane
 - Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Dilip Kumar
 - Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 Masahiko Sawada
 - BUG #18973: The default enable_material=ON affects the cost estimation of optimizer, resulting in 10968x slow PG Bug reporting form
 - Re: BUG #18973: The default enable_material=ON affects the cost estimation of optimizer, resulting in 10968x slow Tom Lane
 - Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane