pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feederror cache lookup failed in plpgsql function
2024-06-18 09:19 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: error cache lookup failed in plpgsql function
2024-06-27 12:57 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
[2+ messages in thread]
PG16 walsender hangs in ResourceArrayEnlarge using pgoutput
2024-06-25 07:52 UTC Bowen Shi <zxwsbg12138@gmail.com>
` RE: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput
2024-06-25 11:47 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput
2024-06-26 05:05 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput
2024-06-26 05:25 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput
2024-06-26 06:30 UTC Bowen Shi <zxwsbg12138@gmail.com>
` RE: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput
2024-06-27 03:31 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: PG16 walsender hangs in ResourceArrayEnlarge using pgoutput
2024-06-27 12:23 UTC Amit Kapila <amit.kapila16@gmail.com>
[7+ messages in thread]
BUG #18523: String compare not consistent
2024-06-26 09:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18523: String compare not consistent
2024-06-26 09:44 UTC Patrick van Dijk <patrick.van.dijk@gmail.com>
` Re: BUG #18523: String compare not consistent
2024-06-26 10:11 UTC Patrick van Dijk <patrick.van.dijk@gmail.com>
` Re: BUG #18523: String compare not consistent
2024-06-26 15:59 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18523: String compare not consistent
2024-06-26 16:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18523: String compare not consistent
2024-06-26 18:30 UTC Peter Eisentraut <peter@eisentraut.org>
[6+ messages in thread]
error "can only drop stats once" brings down database
2024-02-20 17:38 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: error "can only drop stats once" brings down database
2024-02-20 18:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: error "can only drop stats once" brings down database
2024-05-03 18:10 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: error "can only drop stats once" brings down database
2024-05-03 19:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: error "can only drop stats once" brings down database
2024-05-03 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: error "can only drop stats once" brings down database
2024-05-05 16:09 UTC Andres Freund <andres@anarazel.de>
` Re: error "can only drop stats once" brings down database
2024-05-05 22:35 UTC Andres Freund <andres@anarazel.de>
` RE: error "can only drop stats once" brings down database
2024-05-06 08:44 UTC Floris Van Nee <florisvannee@Optiver.com>
` RE: error "can only drop stats once" brings down database
2024-06-02 22:01 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: error "can only drop stats once" brings down database
2024-06-04 05:04 UTC Michael Paquier <michael@paquier.xyz>
` RE: error "can only drop stats once" brings down database
2024-06-05 10:31 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: error "can only drop stats once" brings down database
2024-06-06 04:44 UTC Michael Paquier <michael@paquier.xyz>
` Re: error "can only drop stats once" brings down database
2024-06-06 06:05 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: error "can only drop stats once" brings down database
2024-06-07 01:15 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: error "can only drop stats once" brings down database
2024-06-07 02:46 UTC Michael Paquier <michael@paquier.xyz>
` Re: error "can only drop stats once" brings down database
2024-06-07 03:12 UTC Andres Freund <andres@anarazel.de>
` Re: error "can only drop stats once" brings down database
2024-06-07 09:32 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: error "can only drop stats once" brings down database
2024-06-07 09:49 UTC Michael Paquier <michael@paquier.xyz>
` RE: error "can only drop stats once" brings down database
2024-06-08 11:52 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: error "can only drop stats once" brings down database
2024-06-10 06:37 UTC Michael Paquier <michael@paquier.xyz>
` RE: error "can only drop stats once" brings down database
2024-06-10 15:13 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: error "can only drop stats once" brings down database
2024-06-11 07:44 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: error "can only drop stats once" brings down database
2024-06-14 00:37 UTC Michael Paquier <michael@paquier.xyz>
` Re: error "can only drop stats once" brings down database
2024-06-16 23:28 UTC Michael Paquier <michael@paquier.xyz>
` Re: error "can only drop stats once" brings down database
2024-06-25 00:22 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: error "can only drop stats once" brings down database
2024-06-25 04:00 UTC Michael Paquier <michael@paquier.xyz>
[26+ messages in thread]
BUG #18521: RLS should report when non-select operation is refused
2024-06-24 18:10 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18520: Different results when analyze a relation with UDT.
2024-06-24 10:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18520: Different results when analyze a relation with UDT.
2024-06-24 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-10 14:11 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
` Re: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-13 02:34 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-16 06:27 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-21 14:15 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` RE: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-21 19:40 UTC Kamil ADEM <kamila@aqvilasoftware.com>
` Re: Postgresql 16.3 installation error (setup file) on Windows 11
2024-06-06 13:38 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: Postgresql 16.3 installation error (setup file) on Windows 11
2024-06-24 10:41 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[7+ messages in thread]
Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific)
2024-06-21 14:02 UTC Eric Marsden <eric.marsden@risk-engineering.org>
` Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific)
2024-06-21 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Cache lookup failed for type 34813 (CREATE TYPE AS ENUM + P/B/E insert, processor-specific) / user error
2024-06-21 16:16 UTC Eric Marsden <eric.marsden@risk-engineering.org>
[3+ messages in thread]
BUG #18518: ::timestamp add minutes and seconds to the converted values
2024-06-20 15:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18518: ::timestamp add minutes and seconds to the converted values
2024-06-21 14:21 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18518: ::timestamp add minutes and seconds to the converted values
2024-06-21 14:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)")
2024-06-07 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)")
2024-06-08 22:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)")
2024-06-16 20:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)")
2024-06-16 22:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)")
2024-06-16 23:24 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)")
2024-06-16 23:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)")
2024-06-21 01:54 UTC Michael Paquier <michael@paquier.xyz>
[7+ messages in thread]
BUG #18517: Dropping a table referenced by an initially deferred foreign key fails with an error
2024-06-20 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18517: Dropping a table referenced by an initially deferred foreign key fails with an error
2024-06-20 16:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18516: Foreign key data integrity is not validated when reenabled the trigger on tables
2024-06-20 09:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18516: Foreign key data integrity is not validated when reenabled the trigger on tables
2024-06-20 12:10 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18516: Foreign key data integrity is not validated when reenabled the trigger on tables
2024-06-20 12:53 UTC Mujjamil k <mujjamil995@gmail.com>
` Re: BUG #18516: Foreign key data integrity is not validated when reenabled the trigger on tables
2024-06-20 13:07 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18516: Foreign key data integrity is not validated when reenabled the trigger on tables
2024-06-20 13:31 UTC Mujjamil k <mujjamil995@gmail.com>
` Re: BUG #18516: Foreign key data integrity is not validated when reenabled the trigger on tables
2024-06-20 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
Ynt: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-14 07:40 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
` Re: Ynt: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-21 18:36 UTC Andres Freund <andres@anarazel.de>
` Ynt: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-22 15:11 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
` Ynt: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-22 15:18 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
` Ynt: Postgresql 16.3 installation error (setup file) on Windows 11
2024-06-20 10:34 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
[5+ messages in thread]
BUG #18513: PG17 build on windows generates postgres.exe.lib instead of postgres.lib
2024-06-17 05:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18513: PG17 build on windows generates postgres.exe.lib instead of postgres.lib
2024-06-18 06:25 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #18513: PG17 build on windows generates postgres.exe.lib instead of postgres.lib
2024-06-18 11:32 UTC Muralikrishna Bandaru <muralikrishna.bandaru@enterprisedb.com>
` Re: BUG #18513: PG17 build on windows generates postgres.exe.lib instead of postgres.lib
2024-06-20 07:23 UTC Peter Eisentraut <peter@eisentraut.org>
[4+ messages in thread]
BUG #18486: Is there something wrong with the calculation in ReorderBufferChangeSize()?
2024-05-29 09:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18486: Is there something wrong with the calculation in ReorderBufferChangeSize()?
2024-06-04 05:28 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re:Re: BUG #18486: Is there something wrong with the calculation in ReorderBufferChangeSize()?
2024-06-06 10:05 UTC Michael <xu.xw2008@163.com>
` Re: Re: BUG #18486: Is there something wrong with the calculation in ReorderBufferChangeSize()?
2024-06-19 09:50 UTC Amit Kapila <amit.kapila16@gmail.com>
[4+ messages in thread]
JIT crash introduced by 6185c9737c with LLVM 14
2024-06-14 04:25 UTC Jeff Davis <jeff@j-davis.com>
` Re: JIT crash introduced by 6185c9737c with LLVM 14
2024-06-14 05:57 UTC Amit Langote <amitlangote09@gmail.com>
` Re: JIT crash introduced by 6185c9737c with LLVM 14
2024-06-17 09:32 UTC Amit Langote <amitlangote09@gmail.com>
` Re: JIT crash introduced by 6185c9737c with LLVM 14
2024-06-18 06:11 UTC Amit Langote <amitlangote09@gmail.com>
` Re: JIT crash introduced by 6185c9737c with LLVM 14
2024-06-18 15:20 UTC Jeff Davis <pgsql@j-davis.com>
` Re: JIT crash introduced by 6185c9737c with LLVM 14
2024-06-18 23:03 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: JIT crash introduced by 6185c9737c with LLVM 14
2024-06-18 23:52 UTC Michael Paquier <michael@paquier.xyz>
` Re: JIT crash introduced by 6185c9737c with LLVM 14
2024-06-19 00:09 UTC Amit Langote <amitlangote09@gmail.com>
[8+ messages in thread]
BUG #18510: jsonpath does not support trailing backslash at the end of the query
2024-06-14 20:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18510: jsonpath does not support trailing backslash at the end of the query
2024-06-14 20:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18510: jsonpath does not support trailing backslash at the end of the query
2024-06-14 22:16 UTC Lex Vorona <voronaam@gmail.com>
` Re: BUG #18510: jsonpath does not support trailing backslash at the end of the query
2024-06-18 09:33 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[4+ messages in thread]
BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script
2024-06-17 16:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script
2024-06-17 20:22 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script
2024-06-17 20:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script
2024-06-18 02:03 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script
2024-06-18 02:20 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script
2024-06-18 02:25 UTC Thomas Munro <thomas.munro@gmail.com>
[6+ messages in thread]
BUG #18512: Backend memory leak when using command parameters after generating notifications
2024-06-16 20:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18512: Backend memory leak when using command parameters after generating notifications
2024-06-17 20:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18483: Segmentation fault in tests modules
2024-05-28 03:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-03 22:40 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-07 20:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-07 22:29 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-08 03:17 UTC John Naylor <johncnaylorls@gmail.com>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-08 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-08 15:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-09 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-10 00:33 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-10 05:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-10 06:23 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-10 06:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-10 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-10 23:10 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-11 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18483: Segmentation fault in tests modules
2024-06-17 05:29 UTC Michael Paquier <michael@paquier.xyz>
[16+ messages in thread]
BUG #18511: changing global certificate directory path
2024-06-16 03:08 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18508: Not all packages are present in the repo on rhel 8
2024-06-14 13:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18508: Not all packages are present in the repo on rhel 8
2024-06-15 11:58 UTC Robert Treat <rob@xzilla.net>
[2+ messages in thread]
Previous command not accessible in postgres 17 beta
2024-06-13 05:30 UTC usman khan <usman.khan9805@gmail.com>
` Re: Previous command not accessible in postgres 17 beta
2024-06-13 14:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: [EXTERNAL] Re: Previous command not accessible in postgres 17 beta
2024-06-13 15:08 UTC Wetmore, Matthew (CTR) <Matthew.Wetmore@evernorth.com>
` Re: [EXTERNAL] Re: Previous command not accessible in postgres 17 beta
2024-06-14 05:45 UTC usman khan <usman.khan9805@gmail.com>
[4+ messages in thread]
BUG #18479: websearch_to_tsquery inconsistent behavior for german when using parentheses
2024-05-24 07:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18479: websearch_to_tsquery inconsistent behavior for german when using parentheses
2024-06-13 22:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18479: websearch_to_tsquery inconsistent behavior for german when using parentheses
2024-06-13 23:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2020-12-27 17:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-02-12 12:35 UTC Pawel Kudzia <kudzia@gmail.com>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-06-17 06:40 UTC Pawel Kudzia <kudzia@gmail.com>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-06-17 08:00 UTC Pawel Kudzia <kudzia@gmail.com>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-06-17 14:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-06-17 19:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-06-17 21:55 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-06-17 22:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-06-17 22:10 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-06-22 16:02 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-07-10 21:56 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-07-11 16:14 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-08-02 08:07 UTC Pawel Kudzia <kudzia@gmail.com>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2021-09-06 08:18 UTC Pawel Kudzia <kudzia@gmail.com>
` Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
2024-06-13 18:49 UTC Pawel Kudzia <kudzia@gmail.com>
[15+ 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