View Revisions: Issue #6989
| Summary | 0006989: Limit number of changes requested by the Log Miner from PostgreSQL | ||
|---|---|---|---|
| Revision | 2025-07-07 20:52 by pbelov | ||
| Description | Limit number of changes peeked by the PostgreSQL Log Miner to prevent out-of-memory conditions and long-running cursors consuming lots of database resources. |
||
| Revision | 2025-07-09 13:18 by pbelov | ||
| Description | Limit number of changes requested by the Log Miner from PostgreSQL to prevent out-of-memory conditions and long-running cursors consuming lots of database resources. |
||
| Revision | 2025-07-10 14:13 by pbelov | ||
| Description | Limit number of changes requested by the Log Miner from PostgreSQL to prevent out-of-memory conditions and long-running cursors consuming lots of database resources. Update: with this change Log Miner for PostgreSQL is now more resilient when WAL backlog is putting pressure on resources available to both database engine and SymmetricDS. Administrators can now log.miner.max.request.rows parameter to dial down number of changes PostgreSQL will send to SymmetricDS during one run of the Log miner job. Also, SymmetricDS will mark WAL entries as "consumed" much sooner, allowing PostgreSQL to release resources. Administrators should consider tuning the log.miner.flush.commit.size parameter, which controls how often new data is committed to SymmetricDS runtime table, which also initiates marking WAL entries as "consumed". |
||