| From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Old pg_clog files |
| Date: | 2017-10-29 21:55:25 |
| Message-ID: | f59178b2-7030-e5e0-d443-a453f8d60b95@cox.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/29/2017 03:37 PM, David G. Johnston wrote:
> On Sunday, October 29, 2017, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net
> <mailto:ron(dot)l(dot)johnson(at)cox(dot)net>> wrote:
>
> Hi,
>
> v8.4.17
>
> http://www.postgresql-archive.org/pg-clog-questions-td2080911.html
> <http://www.postgresql-archive.org/pg-clog-questions-td2080911.html>
>
> According to this old thread, doing a VACUUM on every table in the
> postgres, template1 and TAPd databases should remove old pg_clog files.
>
>
> However, while about 40 of them have been deleted, 183 still exist.
> What did I do wrong?
>
>
> Reading the old thread it sounds like it might require multiple vacuums to
> affect complete removal.
I vacuumed them twice.
Does it matter whether I ran a VACUUM ANALYZE on every table instead of
"vacuumdb --all"?
--
World Peace Through Nuclear Pacification
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Farber | 2017-10-30 10:08:22 | Comparing epoch to timestamp |
| Previous Message | David G. Johnston | 2017-10-29 20:37:48 | Re: Old pg_clog files |