Re: does wal archiving block the current client connection?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Frost <jeff(at)frostconsultingllc(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: does wal archiving block the current client connection?
Date: 2006-05-15 18:33:43
Message-ID: 10784.1147718023@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

Jeff Frost <jeff(at)frostconsultingllc(dot)com> writes:
> On Mon, 15 May 2006, Tom Lane wrote:
>> No, I can't see what the connection should be there. It's supposed to
>> be designed so that the archive command can take its sweet old time and
>> nothing happens except that a backlog of WAL files builds up in pg_xlog.

> That's what I thought, but that doesn't seem to be what I'm observing. Of
> course the NAS device only gets wedged about once every month or two, so it's
> difficult to reproduce.

If it's really a PG bug, it should be trivial to reproduce: put a long
sleep in the archive-command script.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jeff Frost 2006-05-15 18:52:41 Re: does wal archiving block the current client connection?
Previous Message Jeff Frost 2006-05-15 18:31:13 Re: does wal archiving block the current client connection?

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Frost 2006-05-15 18:52:41 Re: does wal archiving block the current client connection?
Previous Message Jeff Frost 2006-05-15 18:31:13 Re: does wal archiving block the current client connection?