| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: does wal archiving block the current client connection? |
| Date: | 2006-05-23 04:02:25 |
| Message-ID: | 17816.1148356945@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 tried both pulling the plug on the CIFS server and unsharing the CIFS share,
> but pgbench continued completely unconcerned. I guess the failure mode of the
> NAS device in the customer colo must be something different that I don't yet
> know how to simulate. I suspect I'll have to wait till it happens again and
> try to gather some more data before restarting the NAS device. Thanks for all
> your suggestions guys!
I'm still thinking that the simplest explanation is that $PGDATA/pg_clog/
is on the NAS device. Please double-check the file locations.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Frost | 2006-05-23 04:10:54 | Re: does wal archiving block the current client connection? |
| Previous Message | Jeff Frost | 2006-05-23 03:59:30 | Re: does wal archiving block the current client connection? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Frost | 2006-05-23 04:10:54 | Re: does wal archiving block the current client connection? |
| Previous Message | Jeff Frost | 2006-05-23 03:59:30 | Re: does wal archiving block the current client connection? |