Skip site navigation (1) Skip section navigation (2)

Re: Bug in WAL backup documentation

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org, Bernd Helmle <mailings(at)oopsware(dot)de>, pgsql-patches(at)postgresql(dot)org, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Subject: Re: Bug in WAL backup documentation
Date: 2006-11-08 01:11:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
On Sun, Nov 05, 2006 at 11:49:36 -0500,
  Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> As already discussed upthread, anyone who wants the path can get it from
> `pwd` or local equivalent --- and that mechanism is robust (as long as
> the directory move doesn't happen while any particular instance of the
> script is running).  I don't see why we should go out of our way to
> provide a bad substitute for pwd.

I think you also still need read access to the intervening directories.
If the command works by walking up and matching inode numbers with names,
then it will break if it can't read the names. (For example /bin/pwd
breaks when it can't read a parent directories filenames.)

In response to


pgsql-hackers by date

Next:From: Neil ConwayDate: 2006-11-08 01:23:55
Subject: Re: Uncleared result sets in describeOneTableDetails()
Previous:From: JEAN-PIERRE PELLETIERDate: 2006-11-07 23:47:45
Subject: Re: Index ignored with "is not distinct from", 8.2 beta2

pgsql-patches by date

Next:From: Martijn van OosterhoutDate: 2006-11-08 10:19:54
Subject: Re: [HACKERS] Bug in WAL backup documentation
Previous:From: Hiroshi SaitoDate: 2006-11-07 15:04:46
Subject: patch of Encoding problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group