Re: Big 7.1 open items - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Big 7.1 open items
Date
Msg-id 200006220403.AAA15648@candle.pha.pa.us
Whole thread Raw
In response to Re: Big 7.1 open items  (Chris Bitmead <chrisb@nimrod.itg.telstra.com.au>)
Responses Re: Big 7.1 open items  (Don Baccus <dhogaza@pacifier.com>)
List pgsql-hackers
> > where symloc would be SELECT symloc(loc) and return the value into a
> > variable that is used by pg_dump.  The backend would do the lstat() and
> > return the value to the client.
> 
> I'm wondering if pg_dump should store the location of the tablespace. If
> your machine dies, you get a new machine to re-create the database, you
> may not want the tablespace in the same spot. And text-editing a
> gigabyte file would be extremely painful.

If the symlink create fails in CREATE TABLESPACE, it just creates an
ordinary directory.

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Chris Bitmead
Date:
Subject: Re: Big 7.1 open items
Next
From: Tom Lane
Date:
Subject: Re: Big 7.1 open items