| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)protecne(dot)cl> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_log |
| Date: | 2001-03-06 19:31:19 |
| Message-ID: | 6990.983907079@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)protecne(dot)cl> writes:
> ARAIK, pg_log records which tuples are "active" and which ones are
> obsolete, so I'm not going to delete it.
Actually, it records which transactions committed and which didn't.
So, you can slow the rate of growth of pg_log if you can reduce the
number of transactions used. Consider wrapping sequences of operations
into begin/end blocks.
> I know I can dump and restore from a clean (empty) install,
> but is there a simpler way?
Afraid not. pg_log is critical data.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-03-06 19:39:21 | Re: time to integer |
| Previous Message | Gregory Wood | 2001-03-06 19:30:50 | Re: SQL article |