From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | dagamier <zayasj1(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_repack in cluster |
Date: | 2020-01-11 03:20:59 |
Message-ID: | eab28346-78b3-dfa7-9a94-8c399c261f6c@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1/10/20 10:01 AM, dagamier wrote:
> I have two databases that are clustered. One is my primary (DB1) and the
> other is my secondary (DB2). Both have the same tables and schemas. Could I
> use pg_repack against each of these separately (I am wanting to do this at a
> "by table" level) to clean up dead space that hasn't been returned? Should I
> be doing it this way? I would assume that dead space in DB1 would also exist
> in DB2 as deletes are performed as part of the replication process, but the
> reclamation of space back to the system wouldn't take place? Just curious if
> the fact that the database is being replicated would prevent the needed
> steps from occurring as it's my understanding that you can't drop a table
> that's being replicated between two instances.
Why not use VACUUM?
>
>
>
> --
> Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-01-11 03:51:50 | Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?) |
Previous Message | Stephen Frost | 2020-01-10 21:09:24 | Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?) |