Re: pg_log

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sylvain Simard <sylvain(at)luxolith(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_log
Date: 2000-10-26 04:43:23
Message-ID: 4538.972535403@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Sylvain Simard <sylvain(at)luxolith(dot)com> writes:
> At begin, with a new database the pg_log are 40k
> After many days my pg_log is come 3884k

pg_log grows at the rate of 2 bits per transaction.

> It's possible to initialize it? If yes how...

dump ... initdb ... reload.

> It's possible to do anything to don't pg_log come bigger and bigger...

Try to use fewer transactions, if two bits per concerns you.

regards, tom lane

In response to

  • pg_log at 2000-10-25 21:02:12 from Sylvain Simard

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2000-10-26 14:14:16 Re: Updating multiple bool values crashes backend
Previous Message pgsql-bugs 2000-10-26 04:29:49 Select where (upper(xy)~'.CH'); ..matches also SPACE CH