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

Re: Scanning pg_tablespace from walsender

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Scanning pg_tablespace from walsender
Date: 2011-01-03 15:50:11
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Mon, Jan 3, 2011 at 16:29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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"?

Well, if you just need to find all the files, scan the symlinks in
$PGDATA/pg_tblspc/.  Don't turn a filesystem problem into a catalog

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-01-03 15:52:20
Subject: Re: Scanning pg_tablespace from walsender
Previous:From: Brar PieningDate: 2011-01-03 15:45:16
Subject: Re: Visual Studio 2010/Windows SDK 7.1 support

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