Re: does wal archiving block the current client connection?

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff Frost <jeff(at)frostconsultingllc(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: does wal archiving block the current client connection?
Date: 2006-05-17 14:40:35
Message-ID: 1147876835.2646.227.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On Wed, 2006-05-17 at 10:01 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > You'll have to explain a little more. I checked the archives...
>
> I was thinking of
> http://archives.postgresql.org/pgsql-hackers/2004-01/msg00530.php
> full explanation here:
> http://archives.postgresql.org/pgsql-hackers/2004-01/msg00606.php

Sorry, I see my note looks like I couldn't find it. I meant "I've read
the archives". Thanks though.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Chris Hoover 2006-05-17 15:53:44 Figuring autovacuum settings
Previous Message Tom Lane 2006-05-17 14:01:18 Re: does wal archiving block the current client connection?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-05-17 14:47:20 Re: pg_dump and backslash escapes
Previous Message Tom Lane 2006-05-17 14:40:15 Re: PL/pgSQL 'i = i + 1' Syntax