Skip site navigation (1) Skip section navigation (2)

Re: turning of pg_xlog

From: "Plugge, Joe R(dot)" <JRPlugge(at)west(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Chander Ganesan" <chander(at)otg-nc(dot)com>
Cc: "Jonny" <blubb(at)terminalschmiede(dot)de>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: turning of pg_xlog
Date: 2008-09-30 18:49:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
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(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: Tuesday, September 30, 2008 1:45 PM
To: Chander Ganesan
Cc: Jonny; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] turning of pg_xlog 

Chander Ganesan <chander(at)otg-nc(dot)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

In response to

pgsql-admin by date

Next:From: Chander GanesanDate: 2008-09-30 18:55:19
Subject: Re: turning of pg_xlog
Previous:From: Tom LaneDate: 2008-09-30 18:44:38
Subject: Re: turning of pg_xlog

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group