From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Don Baccus <dhogaza(at)pacifier(dot)com> |
Cc: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Big 7.1 open items |
Date: | 2000-06-22 22:05:38 |
Message-ID: | Pine.BSF.4.21.0006221904350.1098-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Wed, 21 Jun 2000, Don Baccus wrote:
> 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.
Or, modify pg_dump so that it auto-dumps to two files, one for schema, one
for data. then its easier to modify the schema on a large database if
tablespaces change ...
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2000-06-22 22:34:46 | Re: Thoughts on multiple simultaneous code page support |
Previous Message | Bruce Momjian | 2000-06-22 21:22:29 | Re: Interesting mention of PostgreSQL in news |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-22 22:34:27 | Re: Re: [GENERAL] libpq error codes |
Previous Message | Bruce Momjian | 2000-06-22 20:11:56 | Re: Big 7.1 open items |