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

Re: [HACKERS] Bug in WAL backup documentation

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Bruno Wolff III <bruno(at)wolff(dot)to>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Simon Riggs <simon(at)2ndquadrant(dot)com>, 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: [HACKERS] Bug in WAL backup documentation
Date: 2006-11-08 10:19:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
On Tue, Nov 07, 2006 at 07:11:35PM -0600, Bruno Wolff III wrote:
> 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.)

That's system dependant though, Linux getcwd doesn't have that problem
for example. Should probably dig up some documention on which systems
would be affected by this.

Have a ncie day,
Martijn van Oosterhout   <kleptog(at)svana(dot)org>
> From each according to his ability. To each according to his ability to litigate.

In response to

pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2006-11-08 10:20:15
Subject: Re: string_to_array eats too much memory?
Previous:From: Teodor SigaevDate: 2006-11-08 10:03:40
Subject: Re: string_to_array eats too much memory?

pgsql-patches by date

Next:From: Michael MeskesDate: 2006-11-08 10:49:03
Subject: Re: BUG #2741: Double-free on error in ECPGconnect
Previous:From: Bruno Wolff IIIDate: 2006-11-08 01:11:35
Subject: Re: Bug in WAL backup documentation

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