Re: [E] Re: BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672"
John Hutchins <john.hutchins@wicourts.gov>
From: John Hutchins <John.Hutchins@WICOURTS.GOV>
To: Masahiko Sawada <sawada.mshk@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-05-28T19:13:20Z
Lists: pgsql-bugs
Hi, Thanks very much for your reply. > The configuration details would help the investigation. Here are all configs which may be relevant: wal_level = logical max_replication_slots = 20 max_logical_replication_workers = 14 max_wal_senders = 20 wal_keep_size = 4096 max_wal_size = 4GB min_wal_size = 1GB wal_sender_timeout = 300s archive_mode = on archive_command = 'true' archive_timeout = 3600 max_worker_processes = 18 max_connections = 1000 shared_buffers = 10GB maintenance_work_mem = 2GB work_mem = 26214kB effective_cache_size = 30GB effective_io_concurrency = 200 > IIUC this issue could happen especially if there are many concurrent > transactions that perform DDLs. Does this match the workload on your > server? I'm not sure if our workload would contain "many concurrent transactions that perform DDLs." Our workload includes DDLs to create temporary tables and also "ALTER TABLE ENABLE/DISABLE TRIGGER" statements that are single-threaded, but may run concurrently with other DML operations. So, in our workloads, there is a possibility of overlap between DDL (trigger management and temporary table creation) and DML from other sessions. Please let me know if you need any additional details. John Hutchins Wisconsin Court System DBA
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix re-distributing previously distributed invalidation messages during logical decoding.
- d87d07b7ad3b 18.0 landed
- 45c357e0e85d 17.6 landed
- b2ae077205e1 16.10 landed
- fc0fb77c550f 15.14 landed
- 983b3636259b 14.19 landed
- 1230be12f086 13.22 landed