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

Re: Performance of COPY for Archive operations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>,pgsql-hackers-win32(at)postgresql(dot)org
Subject: Re: Performance of COPY for Archive operations
Date: 2004-09-17 15:09:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers-win32
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> Nothing that surprising there, though I think I would like to put a WARNING
> message into the Archiver that triggers if more than CHECKPOINT_SEGMENTS WAL
> files are ready to archive at any one time. Though maybe that would cause
> more problems than it would solve: "Archiving of transaction logs cannot
> keep up with system activity. If this occurs regularly, you should
> reconsider your database-disk layout"

Can't see the value of this.  The problem will be readily apparent from
growth of the pg_xlog directory --- anyone who doesn't notice that
probably isn't perusing the postmaster log either.  Also, once it starts
to bleat, what's going to make it stop?  Filling the disk with warning
messages won't be a constructive improvement on the situation :-(

			regards, tom lane

In response to


pgsql-hackers-win32 by date

Next:From: Magnus HaganderDate: 2004-09-17 19:32:02
Subject: plpython win32
Previous:From: Dave PageDate: 2004-09-17 12:25:19
Subject: Re: tsearch/tsearch2 under Win32?

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