repeated - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-07-02 10:44:51 | repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries (Sergei Kornilov)
Hello Yeah, I think there is a missing copy of the type field: --- a/src/interfaces/libpq/fe-cancel.c +++ b/src/interfaces/libpq/fe-cancel.c
Mailing lists >> pgsql-bugs >> Thread
2025-07-02 03:03:00 | repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries (Maxim Boguk)
On Wed, Jul 2, 2025 at 1:09 AM PG Bug reporting form
Mailing lists >> pgsql-bugs >> Thread
2025-07-02 01:08:57 | repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries (PG Bug reporting form)
repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw timeouted
Mailing lists >> pgsql-bugs >> Thread
2025-06-19 11:47:40 | Re: "unexpected duplicate for tablespace" problem in logical replication (Ashutosh Bapat)
repeatedly with invalid relfilenodes, that would bloat the cache with "kinda useless entries". It's a way to make
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-06-09 17:26:33 | Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with (Tom Lane)
repeat call after SSL_WANT_WRITE, but that seems to be a lie: increasing the length
Mailing lists >> pgsql-bugs >> Thread
2025-06-08 05:07:59 | Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql (Tom Lane)
repeated planning. Does it get any better if you do "set plan_cache
Mailing lists >> pgsql-bugs >> Thread
2025-05-19 15:42:13 | BUG #18935: The optimiser's choice of sort doubles the execution time. (PG Bug reporting form)
repeat: CREATE DATABASE database4 WITH ENCODING 'UTF8' TEMPLATE template0; \c database4; CREATE TABLE IF NOT EXISTS
Mailing lists >> pgsql-bugs >> Thread
2025-05-14 11:18:45 | BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a (PG Bug reporting form)
repeat: CREATE UNLOGGED TABLE IF NOT EXISTS t0(c0 int4range , CHECK((t0.c0) BETWEEN SYMMETRIC (((t0.c0
Mailing lists >> pgsql-bugs >> Thread
2025-04-27 20:05:54 | BUG #18906: EXCEPT with identical left/right queries isn't eliminated (PG Bug reporting form)
repeat? docker pull postgres:latest docker run --name postgres -e POSTGRES_PASSWORD=1213 -d -p 5432:5432 postgres
Mailing lists >> pgsql-bugs >> Thread
2025-04-27 19:49:24 | BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should (PG Bug reporting form)
repeat? docker pull postgres:latest docker run --name postgres -e POSTGRES_PASSWORD=1213 -d -p 5432:5432 postgres
Mailing lists >> pgsql-bugs >> Thread
2025-04-27 19:15:02 | BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan (PG Bug reporting form)
repeat? docker pull postgres:latest docker run --name postgres -e POSTGRES_PASSWORD=1213 -d -p 5432:5432 postgres
Mailing lists >> pgsql-bugs >> Thread
2025-04-12 06:34:59 | BUG #18893: Segfault during analyze pg_database (PG Bug reporting form)
repeat your command. server closed the connection unexpectedly This probably means the server terminated abnormally
Mailing lists >> pgsql-bugs >> Thread
2025-03-29 13:20:24 | Re: BUG #18871: Cross-partition MERGE fails with unclear internal error (Dean Rasheed)
repeating it. I've committed the fix, except that I put the test case
Mailing lists >> pgsql-bugs >> Thread
2025-03-06 04:16:57 | BUG #18832: Segfault in GrantLockLocal (PG Bug reporting form)
repeat your command. 2025-03-06 07:02:39.367 ACDT [446319] FATAL: the database system
Mailing lists >> pgsql-bugs >> Thread
2025-02-17 13:52:32 | BUG #18815: Logical replication worker Segmentation fault (PG Bug reporting form)
repeat again until subscription is disabled. Subscriptions for tables (small) without partitions works fine. There