pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: does wal archiving block the current client connection?
Date: Mon, 15 May 2006 16:39:16 -0500
Message-ID: <1147729156.9755.154.camel@state.g2switchworks.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605151424500.9581@discord.dyndns.org>
References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org>
	<1147728181.5074.73.camel@localhost.localdomain>
	<Pine.LNX.4.64.0605151424500.9581@discord.dyndns.org>

On Mon, 2006-05-15 at 16:29, Jeff Frost wrote:
> On Mon, 15 May 2006, Simon Riggs wrote:
> 
> > On Mon, 2006-05-15 at 09:28 -0700, Jeff Frost wrote:
> >> 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
> >
> > What kind of problems?
> 
> It becomes unwritable for whatever reason CIFS shares become unwritable.  It's 
> a windows 2003 NAS device and a reboot solves the problem, but it leaves no 
> event logs on the windows side of things, so difficult to determine the root 
> cause.

I don't think you need logs to figure out that the problem is that it's
a Windows based NAS device.  :)

Seriously, we had BSD based NAS devices one place I worked, and the
company making them switched to Win2k3 and after we had one or two do
exactly what you're talking about, we just started building our own
based on RedHat or BSD.  Same hardware (we just formatted the drives on
one of the ones that came with w2k3) and we never had another moment's
problem with them.

In other news... Does the archiver actually connect to the database?  



view thread (55+ messages)  latest in thread

Message-ID: <1147729156.9755.154.camel@state.g2switchworks.com>
Permalink:  ../1147729156.9755.154.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1147729156.9755.154.camel@state.g2switchworks.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: smarlowe@g2switchworks.com, jeff@frostconsultingllc.com, simon@2ndquadrant.com
  Subject: Re: does wal archiving block the current client connection?
  In-Reply-To: <1147729156.9755.154.camel@state.g2switchworks.com>
  References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org> <1147728181.5074.73.camel@localhost.localdomain> <Pine.LNX.4.64.0605151424500.9581@discord.dyndns.org> <1147729156.9755.154.camel@state.g2switchworks.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox