Re: turning of pg_xlog

I might have to disagree here.  I personally experienced a scenario
where I had 500 MB of file space defined for my WAL log files and then
attempted (not thinking it through thoroughly) to perform a COPY of a
very large (1.8 GB) dataset and kept adding WAL files until my file
system filled up and then the instance crashed.

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Tuesday, September 30, 2008 1:45 PM
To: Chander Ganesan
Cc: Jonny; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] turning of pg_xlog

Chander Ganesan <chander@otg-nc.com> writes:
> You should also understand that if you set checkpoint_segments to a
> small number, its still possible that PostgreSQL might use more than
> that number for a large transaction.

"Large transactions" have nothing to do with this.  You are confusing
Postgres' implementation with Oracle's.

            regards, tom lane

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin