pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17806: PostgreSQL 13.10 returns "CREATE DATABASE cannot be executed within a pipeline"
2023-02-23 22:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17806: PostgreSQL 13.10 returns "CREATE DATABASE cannot be executed within a pipeline"
2023-02-24 15:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17806: PostgreSQL 13.10 returns "CREATE DATABASE cannot be executed within a pipeline"
2023-02-24 19:36 UTC Wesley Smith <wesley.smith@exterro.com>
[3+ messages in thread]
pg_upgrade does not support a table 2 in the original database to inherit from table 1 (field F_Test1 is not empty), and then table 2 modifies F by itself_ Test1 is nullable
2023-02-24 03:22 UTC 小杨 <17097859508@qq.com>
[PATCH v2] WIP: generate explicit expression step to evaluate correlated MULTIEXPR_SUBLINK
2023-02-24 01:48 UTC Andres Freund <andres@anarazel.de>
[BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-02-08 14:48 UTC Mead, Scott <meads@amazon.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-02-12 20:03 UTC David Zhang <david.zhang@highgo.ca>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-03-02 01:43 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-04-14 14:17 UTC Mead, Scott <meads@amazon.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-05-26 08:00 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-10-26 15:23 UTC Scott Mead <scott@meads.us>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-11-19 18:36 UTC Scott Mead <scott@meads.us>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2021-11-22 04:36 UTC Jobin Augustine <jobin.augustine@percona.com>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2023-01-23 17:23 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2023-01-31 15:35 UTC Scott Mead <scott@meads.us>
` Re: [BUG] Autovacuum not dynamically decreasing cost_limit and cost_delay
2023-02-23 22:22 UTC Melanie Plageman <melanieplageman@gmail.com>
[11+ messages in thread]
BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 09:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 12:54 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 13:02 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 15:51 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 15:59 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 16:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 16:34 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 22:30 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-14 23:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 13:18 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 15:30 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 15:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 16:08 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 16:12 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-15 17:02 UTC reiner peterke <zedaardv@gmail.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 08:07 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 16:03 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 16:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 18:14 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2022-12-16 18:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
2023-02-23 21:07 UTC Daniel Gustafsson <daniel@yesql.se>
[22+ messages in thread]
[PATCH v1] heavily-WIP: partition specific subplan plans
2023-02-22 19:03 UTC Andres Freund <andres@anarazel.de>
Re: pg_dump error
2003-07-29 15:59 UTC Vasko Miovski <vasko.miovski@cybertechne.com>
` pg_dump Error
2004-01-30 13:40 UTC yogesh sailukar <sailukar_yogesh@yahoo.com>
` pg_dump: error
2023-02-22 16:17 UTC Alessandro Papa - Infolab <a.papa@infolabonline.com>
` Re: pg_dump: error
2023-02-22 16:44 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: pg_dump: error
2023-02-22 17:15 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[5+ messages in thread]
BUG #17805: Unexpected results when bounds of FOR loop use non-integer numbers
2023-02-22 14:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17805: Unexpected results when bounds of FOR loop use non-integer numbers
2023-02-22 15:01 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
pg_restore: warning: could not find where to insert IF EXISTS in statement "-- *not* dropping schema, since initdb creates it
2023-02-17 11:21 UTC Samo Dadela <samo.dadela@gmail.com>
` Re: pg_restore: warning: could not find where to insert IF EXISTS in statement "-- *not* dropping schema, since initdb creates it
2023-02-17 18:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_restore: warning: could not find where to insert IF EXISTS in statement "-- *not* dropping schema, since initdb creates it
2023-02-22 09:04 UTC Samo Dadela <samo.dadela@gmail.com>
[3+ messages in thread]
BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-13 05:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-14 05:05 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-14 08:02 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-15 07:12 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-20 07:59 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-20 23:43 UTC Michael Paquier <michael@paquier.xyz>
` RE: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-21 01:05 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-21 04:36 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-21 06:34 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-22 01:07 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17789: process_pgfdw_appname() fails for autovacuum workers
2023-02-22 02:55 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[11+ messages in thread]
Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-20 15:55 UTC Charles <peacech@gmail.com>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-20 16:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-20 16:44 UTC Charles <peacech@gmail.com>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-20 17:15 UTC Charles <peacech@gmail.com>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-20 19:25 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-20 20:58 UTC Stephen Frost <sfrost@snowman.net>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-21 01:38 UTC Charles <peacech@gmail.com>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-21 01:54 UTC Charles <peacech@gmail.com>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-21 02:02 UTC Stephen Frost <sfrost@snowman.net>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-21 02:07 UTC Charles <peacech@gmail.com>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-21 02:22 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-21 02:45 UTC Charles <peacech@gmail.com>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-21 16:35 UTC Stephen Frost <sfrost@snowman.net>
` Re: Query run in 27s with 15.2 vs 37ms with 14.6
2023-02-21 19:08 UTC Jeff Janes <jeff.janes@gmail.com>
[14+ messages in thread]
BUG #17795: Erroneous parsing of floating-poing components in DecodeISO8601Interval()
2023-02-15 07:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17795: Erroneous parsing of floating-poing components in DecodeISO8601Interval()
2023-02-19 23:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17795: Erroneous parsing of floating-poing components in DecodeISO8601Interval()
2023-02-20 10:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17795: Erroneous parsing of floating-poing components in DecodeISO8601Interval()
2023-02-20 21:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Inconsistent 'at time zone' conversion
2023-02-19 22:36 UTC Umut TEKİN <umuttechin@gmail.com>
` Re: Inconsistent 'at time zone' conversion
2023-02-19 23:46 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistent 'at time zone' conversion
2023-02-19 23:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Inconsistent 'at time zone' conversion
2023-02-20 12:54 UTC Umut TEKİN <umuttechin@gmail.com>
` Re: Inconsistent 'at time zone' conversion
2023-02-20 15:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #17802: PGLogical getting Terminated
2023-02-20 12:46 UTC PG Bug reporting form <noreply@postgresql.org>
Create user mapping without password
2023-02-16 10:33 UTC Aymen Rahal <aymen.rahal01@gmail.com>
` Re: Create user mapping without password
2023-02-20 02:00 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[2+ messages in thread]
PostgreSQL Windows Install Log causes errorDump in log
2023-02-19 10:43 UTC Stephen L. De Rudder <sldr22@hotmail.com>
BUG #17797: connection error
2023-02-16 16:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17797: connection error
2023-02-16 19:31 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17794: dates with zero or negative years are not accepted
2023-02-15 04:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17794: dates with zero or negative years are not accepted
2023-02-15 22:06 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17794: dates with zero or negative years are not accepted
2023-02-15 22:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17794: dates with zero or negative years are not accepted
2023-02-15 23:03 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17794: dates with zero or negative years are not accepted
2023-02-16 00:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one
2023-02-15 12:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one
2023-02-15 13:25 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one
2023-02-15 14:03 UTC agharta82@gmail.com <agharta82@gmail.com>
` Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one
2023-02-15 14:09 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one
2023-02-15 14:29 UTC agharta82@gmail.com <agharta82@gmail.com>
[5+ messages in thread]
BUG #17791: Assert on procarray.c
2023-02-14 03:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17791: Assert on procarray.c
2023-02-14 21:04 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17791: Assert on procarray.c
2023-02-15 04:16 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #17791: Assert on procarray.c
2023-02-15 05:06 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17791: Assert on procarray.c
2023-02-15 11:16 UTC Robins Tharakan <tharakan@gmail.com>
[5+ messages in thread]
BUG #17782: ERROR: variable not found in subplan target lists
2023-02-07 13:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17782: ERROR: variable not found in subplan target lists
2023-02-07 13:43 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17782: ERROR: variable not found in subplan target lists
2023-02-08 15:42 UTC Dmytro Hanzhelo <d.hanzhelo@indevlab.com>
` Re: BUG #17782: ERROR: variable not found in subplan target lists
2023-02-14 12:51 UTC Alexander Bluce <amateur@indevlab.com>
` Re: BUG #17782: ERROR: variable not found in subplan target lists
2023-02-14 16:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17782: ERROR: variable not found in subplan target lists
2023-02-15 05:41 UTC Alexander Bluce <amateur@indevlab.com>
[6+ messages in thread]
BUG #17793: Query with large number of joins crashes PostgreSQL
2023-02-14 09:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17793: Query with large number of joins crashes PostgreSQL
2023-02-14 11:51 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #17793: Query with large number of joins crashes PostgreSQL
2023-02-14 14:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17793: Query with large number of joins crashes PostgreSQL
2023-02-14 15:59 UTC Joe Conway <mail@joeconway.com>
` Re: BUG #17793: Query with large number of joins crashes PostgreSQL
2023-02-14 16:35 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #17793: Query with large number of joins crashes PostgreSQL
2023-02-15 02:00 UTC Stephen Frost <sfrost@snowman.net>
[6+ messages in thread]
BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-01-25 11:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-01-31 12:27 UTC Gunnar "Nick" Bluth <gunnar.bluth@pro-open.de>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-05 01:28 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-08 16:11 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-09 08:24 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-09 21:54 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-09 22:22 UTC Jacob Champion <jchampion@timescale.com>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-09 22:45 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-10 00:24 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-10 06:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-10 09:33 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-10 14:02 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-11 00:13 UTC Jacob Champion <jchampion@timescale.com>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-11 10:58 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-13 01:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-13 12:54 UTC Gunnar "Nick" Bluth <gunnar.bluth@pro-open.de>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-13 17:44 UTC Jacob Champion <jchampion@timescale.com>
` Re: BUG #17760: SCRAM authentication fails with "modern" (rsassaPss signature) server certificate
2023-02-15 01:22 UTC Michael Paquier <michael@paquier.xyz>
[18+ messages in thread]
BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-06 14:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-10 23:02 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-10 23:06 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-10 23:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-10 23:20 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-10 23:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-11 00:49 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-11 01:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-11 01:51 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-12 10:30 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-12 16:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-13 00:31 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-13 00:46 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-13 00:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-13 03:21 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-13 05:29 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-13 05:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17777: An assert failed in nodeWindowAgg.c
2023-02-13 19:45 UTC Andres Freund <andres@anarazel.de>
[18+ messages in thread]
WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-05 15:23 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-16 05:05 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-17 06:53 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-17 09:13 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-17 09:14 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-18 11:21 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-18 11:27 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-19 02:00 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-19 09:46 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-19 10:02 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-19 10:20 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-19 10:44 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-19 11:09 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-19 11:11 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-10-20 11:55 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-11 14:50 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-13 08:06 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-14 11:38 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-14 12:17 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-14 13:00 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-14 13:11 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-14 13:24 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-14 13:33 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-14 16:22 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-14 16:51 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-15 02:20 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-15 04:51 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-15 05:11 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-15 07:55 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-15 09:01 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-15 14:59 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-16 04:22 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-16 06:13 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-16 06:38 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-16 07:13 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-17 01:17 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-17 04:06 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-17 07:25 UTC Andres Freund <andres@anarazel.de>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-17 08:02 UTC Andres Freund <andres@anarazel.de>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-17 10:26 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-17 14:22 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-17 15:55 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-17 18:55 UTC Andres Freund <andres@anarazel.de>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-18 11:27 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-21 14:26 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-21 20:08 UTC Andres Freund <andres@anarazel.de>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-22 03:36 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-11-22 08:48 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2022-12-08 11:13 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2023-02-06 08:25 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2023-02-06 11:15 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2023-02-06 14:18 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2023-02-06 15:22 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2023-02-07 08:20 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2023-02-10 14:31 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2023-02-13 06:45 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
2023-02-13 19:41 UTC Andres Freund <andres@anarazel.de>
[57+ 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