Re: Big 7.1 open items

> At 01:43 PM 6/22/00 +1000, Chris Bitmead wrote:
> 
> >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.
> 
> So you don't dump your create tablespace statements, recognizing that on
> a new machine (due to upgrades or crashing) you might assign them to
> different directories/mount points/whatever.  That's the reason for
> wanting to hide physical allocation in tablespaces ... the rest of
> your datamodel doesn't need to know.
> 
> Or you do dump your tablespaces, and knowing the paths assigned
> to various ones set up your new machine accordingly.

I imagine we will have a -l flag to pg_dump to dump tablespace
locations.  If they exist on the new machine, we use them.  If not, we
create just directories with no symlinks.


--  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