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:29:36
Message-ID: 19432.1294068576@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-01-03 15:31:07 Re: and it's not a bunny rabbit, either
Previous Message Magnus Hagander 2011-01-03 15:25:28 Scanning pg_tablespace from walsender