| From: | pet(dot)slavov(at)gmail(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #12910: Memory leak with logical decoding |
| Date: | 2015-03-27 09:47:57 |
| Message-ID: | 20150327094757.2488.58808@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 12910
Logged by: Peter Slavov
Email address: pet(dot)slavov(at)gmail(dot)com
PostgreSQL version: 9.4.1
Operating system: Debian wheezy
Description:
Hi,
I am trying to use logical decoding to replay the data modifying queries on
a different server, to synchronize some of the tables. The primary server
has some load, but not so much. I am getting the changes with
pg_logical_slot_get_changes limiting the changes to 50 at a time.
At some point pg_logical_slot_get_changes queries become slow and starts to
eat all the ram and swap, which eventually kills the primary database with
this error:
FATAL: the database system is in recovery mode.
The nature of changes on the primary can have a lot of data in one
transaction. Which I guess is the reason of the slow
pg_logical_slot_get_changes.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-03-27 12:32:38 | Re: Re: BUG #12885: The result of casting a double to an integer depends on the database version |
| Previous Message | dreamsxin | 2015-03-27 08:51:50 | BUG #12909: pg_dump error |