pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17392: archiver process exited with exit code 2 was unexpectedly cause for immediate shutdown request
2022-02-03 01:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #17392: archiver process exited with exit code 2 was unexpectedly cause for immediate shutdown request
2022-02-03 08:52 UTC Sergei Kornilov <sk@zsrv.org>
` RE: Re:BUG #17392: archiver process exited with exit code 2 was unexpectedly cause for immediate shutdown request
2022-02-03 09:54 UTC Улаев Александр Сергеевич <alexander.ulaev@rtlabs.ru>
` Re:BUG #17392: archiver process exited with exit code 2 was unexpectedly cause for immediate shutdown request
2022-02-03 10:06 UTC Sergei Kornilov <sk@zsrv.org>
` RE: Re:BUG #17392: archiver process exited with exit code 2 was unexpectedly cause for immediate shutdown request
2022-02-03 10:29 UTC Улаев Александр Сергеевич <alexander.ulaev@rtlabs.ru>
[5+ messages in thread]
BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-01-28 13:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-01-28 14:17 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-01-29 02:34 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-01-29 03:00 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-01-29 05:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-01-29 15:23 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-01-30 03:43 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-02-02 09:24 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table
2022-02-02 21:01 UTC Andres Freund <andres@anarazel.de>
[9+ messages in thread]
BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
2022-01-11 10:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
2022-01-11 22:19 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
2022-01-12 14:21 UTC Pasi Eronen <eronenp@gmail.com>
` Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
2022-01-13 15:12 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
2022-01-13 15:22 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
2022-02-02 14:39 UTC Pasi Eronen <pe@iki.fi>
` Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
2022-02-02 15:46 UTC Pasi Eronen <pe@iki.fi>
` Re: BUG #17362: Error "could not find block containing chunk" when using index with icu collation on CentOS 7
2022-02-02 17:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
[8+ messages in thread]
BUG #17389: pg_repack creates race conditions on streaming replicas
2022-01-31 16:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17389: pg_repack creates race conditions on streaming replicas
2022-01-31 21:54 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17389: pg_repack creates race conditions on streaming replicas
2022-02-01 08:43 UTC Nick Cleaton <nick@cleaton.net>
` Re: BUG #17389: pg_repack creates race conditions on streaming replicas
2022-02-01 15:25 UTC Ben Chobot <bench@silentmedia.com>
` Re: BUG #17389: pg_repack creates race conditions on streaming replicas
2022-02-01 21:28 UTC Ben Chobot <bench@silentmedia.com>
[5+ messages in thread]
BUG #17390: Function, to_date() -- unexpected values and a request
2022-02-01 00:01 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #17390: Function, to_date() -- unexpected values and a request
2022-02-01 05:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17390: Function, to_date() -- unexpected values and a request
2022-02-01 15:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17390: Function, to_date() -- unexpected values and a request
2022-02-01 20:35 UTC smk_va@yahoo.com <smk_va@yahoo.com>
[4+ messages in thread]
BUG #17388: postgis cant be installed on postgres 11 and centos 7
2022-01-31 08:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17388: postgis cant be installed on postgres 11 and centos 7
2022-02-01 00:17 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #17388: postgis cant be installed on postgres 11 and centos 7
2022-02-01 07:44 UTC Patrik Uytterhoeven <patrik@open-future.be>
[3+ messages in thread]
BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
2022-01-20 14:35 UTC PG Bug reporting form <noreply@postgresql.org>
` RE: BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
2022-01-21 09:53 UTC B Ganesh Kishan <bkishan@commvault.com>
` Re: BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
2022-01-21 15:10 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
2022-01-21 15:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
2022-01-24 05:55 UTC B Ganesh Kishan <bkishan@commvault.com>
` RE: BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
2022-01-27 13:59 UTC B Ganesh Kishan <bkishan@commvault.com>
` Re: BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
2022-01-27 14:16 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` RE: BUG #17375: RECOVERY TARGET TIME RESTORE IS FAILING TO START SERVER
2022-01-31 12:00 UTC B Ganesh Kishan <bkishan@commvault.com>
[8+ messages in thread]
Report a potential bug caused by a improper call to pfree()
2022-01-30 02:47 UTC wliang@stu.xidian.edu.cn
` Re: Report a potential bug caused by a improper call to pfree()
2022-01-30 13:36 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: Report a potential bug caused by a improper call to pfree()
2022-01-30 15:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Report a potential bug caused by a improper call to pfree()
2022-01-31 02:41 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[4+ messages in thread]
Missing include in float.h
2022-01-30 16:32 UTC Ian R. Campbell <ian.campbell@thepathcentral.com>
` Re: Missing include in float.h
2022-01-30 18:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
2022-01-28 17:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
2022-01-28 20:19 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
2022-01-28 20:28 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
2022-01-28 21:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
2022-01-28 21:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
2022-01-28 23:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
2022-01-29 03:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ messages in thread]
BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the
2022-01-26 08:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the
2022-01-26 15:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the
2022-01-28 13:42 UTC 两个孩子的爹 <1726002692@qq.com>
` Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the
2022-01-28 16:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2021-12-25 10:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2021-12-25 23:26 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2021-12-28 13:14 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2021-12-31 07:36 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2021-12-31 12:32 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2022-01-02 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2022-01-04 08:03 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2022-01-07 06:15 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2022-01-08 04:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2022-01-08 08:57 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2022-01-08 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance
2022-01-27 07:25 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
[12+ messages in thread]
BUG #17354: pg_hba_file_rules always shows verify-ca when auth_method=cert
2022-01-04 14:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17354: pg_hba_file_rules always shows verify-ca when auth_method=cert
2022-01-26 09:03 UTC Magnus Hagander <magnus@hagander.net>
[2+ messages in thread]
回复：BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the
2022-01-26 08:29 UTC 两个孩子的爹 <1726002692@qq.com>
BUG #17381: psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" After installing
2022-01-25 02:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17381: psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" After installing
2022-01-25 11:38 UTC Matti Linnanvuori <matti.linnanvuori@portalify.com>
[2+ messages in thread]
BUG #17379: Cannot issue multi-command statements using a replication connection
2022-01-24 01:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17379: Cannot issue multi-command statements using a replication connection
2022-01-24 14:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17379: Cannot issue multi-command statements using a replication connection
2022-01-24 19:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17378: WRONG VALUE ON - A.2. Time Zones
2022-01-23 02:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17378: WRONG VALUE ON - A.2. Time Zones
2022-01-23 19:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17376: Adding unique column with a function() default results in "could not read block 0 in file" error
2022-01-21 09:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17376: Adding unique column with a function() default results in "could not read block 0 in file" error
2022-01-21 17:27 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #17376: Adding unique column with a function() default results in "could not read block 0 in file" error
2022-01-21 17:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17376: Adding unique column with a function() default results in "could not read block 0 in file" error
2022-01-22 00:18 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #17376: Adding unique column with a function() default results in "could not read block 0 in file" error
2022-01-22 04:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17376: Adding unique column with a function() default results in "could not read block 0 in file" error
2022-01-22 06:33 UTC David G. Johnston <david.g.johnston@gmail.com>
[6+ messages in thread]
Further information on BUG #17299: Exit code 3 when open connections concurrently (PQisthreadsafe() == 1)
2022-01-21 02:00 UTC Liam Bowen <liambowen@gmail.com>
` Re: Further information on BUG #17299: Exit code 3 when open connections concurrently (PQisthreadsafe() == 1)
2022-01-21 03:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Further information on BUG #17299: Exit code 3 when open connections concurrently (PQisthreadsafe() == 1)
2022-01-21 05:29 UTC Liam Bowen <liambowen@gmail.com>
` Re: Further information on BUG #17299: Exit code 3 when open connections concurrently (PQisthreadsafe() == 1)
2022-01-21 20:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Query on postgres_fdw extension
2021-05-13 10:46 UTC Swathi P <swathi.bluepearl@gmail.com>
` Re: Query on postgres_fdw extension
2021-05-13 12:04 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Query on postgres_fdw extension
2021-05-14 07:07 UTC Swathi P <swathi.bluepearl@gmail.com>
` Re: Query on postgres_fdw extension
2021-05-14 12:10 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Query on postgres_fdw extension
2021-05-14 14:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query on postgres_fdw extension
2021-05-14 15:10 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Query on postgres_fdw extension
2021-05-14 15:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query on postgres_fdw extension
2021-05-14 16:04 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Query on postgres_fdw extension
2021-06-01 10:01 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: Query on postgres_fdw extension
2021-06-01 10:24 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Query on postgres_fdw extension
2021-06-01 15:09 UTC Swathi P <swathi.bluepearl@gmail.com>
` Re: Query on postgres_fdw extension
2022-01-20 15:59 UTC Duarte Carreira <dncarreira@gmail.com>
` Re: Query on postgres_fdw extension
2022-01-20 17:38 UTC Vijaykumar Jain <vijaykumarjain.github@gmail.com>
` Re: Query on postgres_fdw extension
2022-01-21 12:02 UTC Duarte Carreira <dncarreira@gmail.com>
` Re: Query on postgres_fdw extension
2022-01-21 13:59 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Query on postgres_fdw extension
2022-01-21 14:33 UTC Duarte Carreira <dncarreira@gmail.com>
` Re: Query on postgres_fdw extension
2022-01-21 15:54 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Query on postgres_fdw extension
2022-01-21 16:26 UTC Shaozhong SHI <shishaozhong@gmail.com>
[18+ messages in thread]
BUG #17373: Missing rhel-8.3-x86_64 yum repository dir for postgresql 14
2022-01-20 06:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17373: Missing rhel-8.3-x86_64 yum repository dir for postgresql 14
2022-01-21 09:41 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #17372: Altering statistics during concurrent drop can lead to a server crash
2022-01-20 04:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17372: Altering statistics during concurrent drop can lead to a server crash
2022-01-20 17:57 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17372: Altering statistics during concurrent drop can lead to a server crash
2022-01-21 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
[3+ messages in thread]
BUG #17374: Bug in restore
2022-01-20 09:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17374: Bug in restore
2022-01-20 14:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17371: Immutable INTERVAL to TEXT cast can cause incorrect query results
2022-01-19 21:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17371: Immutable INTERVAL to TEXT cast can cause incorrect query results
2022-01-19 21:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17370: shmem lost on segfault
2022-01-19 03:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17370: shmem lost on segfault
2022-01-19 09:28 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17370: shmem lost on segfault
2022-01-19 09:34 UTC RekGRpth <rekgrpth@gmail.com>
` Re: BUG #17370: shmem lost on segfault
2022-01-19 09:46 UTC Julien Rouhaud <rjuju123@gmail.com>
[4+ 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