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:23:09 |
Message-ID: | 10692.1147717389@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:
> I've run into a problem with a PITR setup at a client. The problem is that
> whenever the CIFS NAS device that we're mounting at /mnt/pgbackup has
> problems, it seems that the current client connection gets blocked and this
> eventually builds up to a "sorry, too many clients already" error. I'm
> wondering if this is expected behavior with the archive command
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.
What PG version is this exactly? Are you sure that the only connection
of the NAS device to PG operations is through the archive script, ie,
you don't have any part of the normal PG data directory mounted on it?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Frost | 2006-05-15 18:31:13 | Re: does wal archiving block the current client connection? |
Previous Message | Xu, Xiaoyi (Rocky) FSM | 2006-05-15 17:56:16 | Re: Error in MS Access |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Frost | 2006-05-15 18:31:13 | Re: does wal archiving block the current client connection? |
Previous Message | Tom Lane | 2006-05-15 18:18:03 | Re: Compression and on-disk sorting |