pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17658: Download release 15 without success
2022-10-20 15:06 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17655: crash postgres by query
2022-10-20 14:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17655: crash postgres by query
2022-10-20 14:50 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17655: crash postgres by query
2022-10-20 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17657: Documentation links color
2022-10-20 14:57 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17624: Creating database is non-ending execution.
2022-09-29 08:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17624: Creating database is non-ending execution.
2022-09-29 14:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17624: Creating database is non-ending execution.
2022-09-29 14:40 UTC Bertrand Mutangana <ishimweb123@gmail.com>
` Re: BUG #17624: Creating database is non-ending execution.
2022-10-19 18:47 UTC Andres Freund <andres@anarazel.de>
[4+ messages in thread]
BUG #17653: Bad handling of NUMERIC data type using ODBC driver version 13.2
2022-10-19 18:18 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17651: Possible optimization for sort on not nullable field (indexed)
2022-10-19 10:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17651: Possible optimization for sort on not nullable field (indexed)
2022-10-19 12:51 UTC Julien Rouhaud <rjuju123@gmail.com>
[2+ messages in thread]
BUG #17650: For the sixth time, the clipping function in the 120 partition table planning stage fails
2022-10-18 13:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17650: For the sixth time, the clipping function in the 120 partition table planning stage fails
2022-10-18 13:50 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17650: For the sixth time, the clipping function in the 120 partition table planning stage fails
2022-10-18 14:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17650: For the sixth time, the clipping function in the 120 partition table planning stage fails
2022-10-19 02:21 UTC Andy Fan <zhihui.fan1213@gmail.com>
[4+ messages in thread]
Aw: Re: BUG #17647: 12.12 package has difference on ubuntu 18.04
2022-10-18 18:13 UTC Mike Fröhner <mikefroehner@gmx.de>
` Re: Aw: Re: BUG #17647: 12.12 package has difference on ubuntu 18.04
2022-10-18 21:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17649: With libpg5 15.0 psql 10.22 uses HOME variable instead of uid and /etc/passwd to select .pgpass file
2022-10-18 09:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17649: With libpg5 15.0 psql 10.22 uses HOME variable instead of uid and /etc/passwd to select .pgpass file
2022-10-18 13:29 UTC Julien Rouhaud <rjuju123@gmail.com>
[2+ messages in thread]
BUG #17647: 12.12 package has difference on ubuntu 18.04
2022-10-17 14:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17647: 12.12 package has difference on ubuntu 18.04
2022-10-18 13:25 UTC Julien Rouhaud <rjuju123@gmail.com>
[2+ messages in thread]
Aw: BUG #17647: 12.12 package has difference on ubuntu 18.04
2022-10-18 08:19 UTC Mike Fröhner <mikefroehner@gmx.de>
` Re: Aw: BUG #17647: 12.12 package has difference on ubuntu 18.04
2022-10-18 12:44 UTC Julien Rouhaud <rjuju123@gmail.com>
[2+ messages in thread]
BUG #17646: create rule named "_RETURN" will cause pg core
2022-10-17 12:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17646: create rule named "_RETURN" will cause pg core
2022-10-17 14:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17646: create rule named "_RETURN" will cause pg core
2022-10-17 14:33 UTC Ilya Anfimov <ilan@tzirechnoy.com>
` Re: BUG #17646: create rule named "_RETURN" will cause pg core
2022-10-17 14:38 UTC Ilya Anfimov <ilan@tzirechnoy.com>
` Re: BUG #17646: create rule named "_RETURN" will cause pg core
2022-10-17 14:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17646: create rule named "_RETURN" will cause pg core
2022-10-17 15:15 UTC Ilya Anfimov <ilan@tzirechnoy.com>
[6+ messages in thread]
BUG #17645: Strange queries that stuck in database system
2022-10-16 23:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17645: Strange queries that stuck in database system
2022-10-17 08:15 UTC Julien Rouhaud <rjuju123@gmail.com>
[2+ messages in thread]
BUG #17637: case-when branches taken even if they dont match, raising errors
2022-10-13 02:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17637: case-when branches taken even if they dont match, raising errors
2022-10-13 11:30 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17637: case-when branches taken even if they dont match, raising errors
2022-10-13 14:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17637: case-when branches taken even if they dont match, raising errors
2022-10-13 20:11 UTC Facundo Etchezar <hctf90@gmail.com>
` Re: BUG #17637: case-when branches taken even if they dont match, raising errors
2022-10-14 13:28 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17637: case-when branches taken even if they dont match, raising errors
2022-10-17 01:14 UTC Facundo Etchezar <hctf90@gmail.com>
[6+ messages in thread]
BUG #17644: EXPLAIN VERBOSE fails on query with SEARCH BREADTH FIRST
2022-10-16 16:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17644: EXPLAIN VERBOSE fails on query with SEARCH BREADTH FIRST
2022-10-16 23:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17641: postgresql service persistently restarts because "could not open shared memory segment"
2022-10-15 18:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17641: postgresql service persistently restarts because "could not open shared memory segment"
2022-10-16 03:31 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17641: postgresql service persistently restarts because "could not open shared memory segment"
2022-10-16 21:05 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17641: postgresql service persistently restarts because "could not open shared memory segment"
2022-10-16 21:11 UTC Andres Freund <andres@anarazel.de>
[4+ messages in thread]
BUG #17640: fork off the requested timeline before the switchpoint.
2022-10-14 05:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17640: fork off the requested timeline before the switchpoint.
2022-10-15 02:47 UTC Michael Paquier <michael@paquier.xyz>
[2+ messages in thread]
BUG #17639: Failed to download packages: python3-humanize-3.13.1-42.rhel8.noarch: Cannot download, all mirrors w
2022-10-13 18:10 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17638: Versioning Policy page appears incorrect
2022-10-13 16:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17638: Versioning Policy page appears incorrect
2022-10-13 17:50 UTC Magnus Hagander <magnus@hagander.net>
[2+ messages in thread]
Default framing option RANGE adds cost for no gain to some window functions
2022-10-09 23:45 UTC Erwin Brandstetter <brsaweda@gmail.com>
` Re: Default framing option RANGE adds cost for no gain to some window functions
2022-10-10 04:21 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Default framing option RANGE adds cost for no gain to some window functions
2022-10-13 15:22 UTC Erwin Brandstetter <brsaweda@gmail.com>
[3+ messages in thread]
BUG #17635: The behavior of quote_ident differs from what the doc specifies
2022-10-11 18:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17635: The behavior of quote_ident differs from what the doc specifies
2022-10-11 19:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
2022-10-11 09:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
2022-10-11 10:05 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
2022-10-11 12:09 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
2022-10-11 12:29 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
2022-10-11 13:16 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
2022-10-11 14:35 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
2022-10-11 15:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
2022-10-11 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17633: Define rule on views which do insert to another relation trigger cache lookup failed error.
2022-10-11 16:16 UTC Japin Li <japinli@hotmail.com>
[9+ messages in thread]
BUG #17634: Inconsistent view_definition in information_schema.views
2022-10-11 13:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17634: Inconsistent view_definition in information_schema.views
2022-10-11 14:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: BUG #17634: Inconsistent view_definition in information_schema.views
2022-10-11 15:57 UTC Blum, Kimber <kimber7@illinois.edu>
[3+ messages in thread]
BUG #17632: a potential bug of memory leak
2022-10-11 02:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17632: a potential bug of memory leak
2022-10-11 09:12 UTC Japin Li <japinli@hotmail.com>
[2+ messages in thread]
Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-09-05 10:19 UTC Dmitriy Kuzmin <kuzmin.db4@gmail.com>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-09-05 12:13 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-09-06 06:38 UTC Dmitriy Kuzmin <kuzmin.db4@gmail.com>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-10-04 22:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-10-04 23:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-10-05 00:15 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-10-05 01:41 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-10-05 15:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-10-05 19:00 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-10-10 12:24 UTC Simon Riggs <simon.riggs@enterprisedb.com>
` Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
2022-10-11 06:48 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[11+ 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