| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Whitney <swhitney(at)journyx(dot)com> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_clog not getting cleared |
| Date: | 2010-12-22 21:38:12 |
| Message-ID: | 10705.1293053892@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Scott Whitney <scott(at)journyx(dot)com> writes:
> I understand the purpose of the clogs, but I would think that the transactions would have been frozen on all dbs (I've got about 300 in my cluster) by now. My logs go back to July 13th which, I think, is when the server was last restarted.
It doesn't really try to remove clog entries that are younger than
vacuum_freeze_table_age (see also vacuum_freeze_min_age). At two bits
per transaction, the general feeling is that eating the disk space is
better than forcing full-database vacuums more often. But if you're
hot to have the space released sooner, those are the knobs to frob.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-12-22 22:30:27 | Re: Securing a remotely accessible PostgreSQL server |
| Previous Message | Scott Whitney | 2010-12-22 21:12:39 | Re: pg_clog not getting cleared |