From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Martín Fernández <fmartin91(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Logical Replication and table bloat |
Date: | 2020-06-05 19:59:52 |
Message-ID: | 9ff805fa-85b0-28b9-44e6-1130a2f14f9d@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/5/20 12:53 PM, Martín Fernández wrote:
> Hello,
>
> Yesterday we stumbled upon a performance issue that we were not expecting. We are replicating our database using AWS DMS which uses logical replication to capture changes. We have some hot tables that get updated very regularly and with the DMS turned on we started noticing that in those table, table bloat increased considerably ~15 times more free_tuples than the average.
>
> When doing logical replication, the subscriber will hold the tuples that could be flagged for reuse until they are sent ? Just trying to understand a little bit better how the logical replication is affecting the vacuuming.
A question for the AWS folks:
https://forums.aws.amazon.com/forum.jspa?forumID=60
>
> Thanks before hand!
>
> Best,
> Martín
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-06-05 20:54:12 | Re: Logical Replication and table bloat |
Previous Message | Ron | 2020-06-05 19:54:27 | Re: Oracle vs. PostgreSQL - a comment |