On Mon, Jan 3, 2011 at 16:29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> I'm working on completing Heikki's patch for streaming base backups,
>> and have run into a problem:
>> In order to dump all tablespaces properly, I have to know where they
>> are (d'uh). In order to do that, I need to scan pg_tablespace.
> Wait a minute. Isn't this problem about to metastasize into "I need to
> read *every* global catalog from walsender"? If not, why not? If so,
> I think we need another answer.
Um, why would I need that? I need to be able to find all files, which
means I need to find all tablespaces. I don't see how that would turn
into "every global catalog"?
(It already needs pg_authid and similar for the login, but that's
shared with all others)
In response to
pgsql-hackers by date
|Next:||From: Magnus Hagander||Date: 2011-01-03 15:37:40|
|Subject: Re: Scanning pg_tablespace from walsender|
|Previous:||From: Andrew Dunstan||Date: 2011-01-03 15:35:14|
|Subject: Re: Visual Studio 2010/Windows SDK 7.1 support|