Re: restoring from dump

Hi Alvaro,

> Note that these files use only 2 bits per transaction,
> so in 24756 bytes you have enough room to cover 99024
> transactions. Furthermore, they always grow in 8192-
> byte increments.

I just did:
-bash-3.00$ pwd; date; ll
and it told me:
/usr/local/pgsql/data/pg_clog
Wed Aug 27 09:09:04 PDT 2008
total 32
-rw------- 1 postgres postgres 32768 Aug 27 02:33 0000

Yesterday the byte count was 24576.
Voila! 24576 + 8192 -> 32768

Regards,

Tena Sakai
tsakai(at)gallo(dot)ucsf(dot)edu

-----Original Message-----
From: Alvaro Herrera [mailto:alvherre(at)commandprompt(dot)com]
Sent: Tue 8/26/2008 7:29 AM
To: Tena Sakai
Cc: Marcelo Martins; jeff(at)frostconsultingllc(dot)com; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] restoring from dump

Tena Sakai wrote:
> Hi Alvaro,
>
> I just looked in pg_clog directory and there is
> only one file:
> -rw------- 1 postgres postgres 24576 Aug 25 20:18 0000
> I saw the same file about 10:30 am and I believe
> it was roughly the same size. This is a brand new
> installation of 8.3.3.

Maybe initdb was executed? That would cause the files to disappear.
Of course, so would the data; it would have to be restored from a
backup.

Note that these files use only 2 bits per transaction, so in 24756 bytes
you have enough room to cover 99024 transactions. Furthermore, they
always grow in 8192-byte increments.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.