From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | andres(at)invisible(dot)email, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18027: Logical replication taking forever |
Date: | 2023-07-19 04:19:30 |
Message-ID: | CAA4eK1JXWXhWLq6Rw7Ev8eQN8=MX20wmu4AFpWBT8fGJV3iUfg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Jul 18, 2023 at 11:08 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 18027
> Logged by: Andres Martin del Campo Campos
> Email address: andres(at)invisible(dot)email
> PostgreSQL version: 13.2
> Operating system: PostgreSQL 13.2 on x86_64-pc-linux-gnu, compiled b
> Description:
>
> I'm trying to use logical replication to replicate a table of 69GB it's been
> a week and it hasn't synced but the table says (in the database where I'm
> replicating this table) is now 400GB and I'm running out of space. What's
> wrong, first I thought it was because of all the WAL logs but I'm now
> assuming it's something else.
>
This sounds a bit unusual. Have you verified the size of tables on
both publisher and subscriber? Can you once show the values of
pg_subscription_rel for this table? Are there any operations happening
on this table either on publisher or subscriber?
--
With Regards,
Amit Kapila.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Martin del Campo Campos | 2023-07-19 04:59:02 | Re: BUG #18027: Logical replication taking forever |
Previous Message | Sergei Kornilov | 2023-07-18 16:19:25 | Re: BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data |