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:29:36
Message-ID: 19432.1294068576@sss.pgh.pa.us (view raw or flat)
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

pgsql-hackers by date

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

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