| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | andres(at)invisible(dot)email |
| Subject: | BUG #18027: Logical replication taking forever |
| Date: | 2023-07-17 22:33:07 |
| Message-ID: | 18027-75ad58d885bd3ae3@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: 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. Anyone has experienced something like this?
You help is much appreciated.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul De Audney | 2023-07-17 23:27:21 | Re: Query returns error "there is no parameter $1" but server logs that there are two parameters supplied |
| Previous Message | Walker Philips | 2023-07-17 21:41:09 | Bug with aggregate Window Functions when using Order By. Elements dropped if order by provided |