Re: Big 7.1 open items

From: "Philip J(dot) Warner" <pjw(at)rhyme(dot)com(dot)au>
To: Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Big 7.1 open items
Date: 2000-06-22 06:32:56
Message-ID: 3.0.5.32.20000622163256.00cb3930@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

At 13:43 22/06/00 +1000, Chris Bitmead wrote:
>Bruce Momjian 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.
>

This is a very good point; the way Dec/RDB gets around it is to allow the
'pg_restore' command to override storage settings when restoring a backup
file.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-06-22 06:59:36 Re: Thoughts on multiple simultaneous code page support
Previous Message Philip J. Warner 2000-06-22 06:31:33 Re: Big 7.1 open items

Browse pgsql-patches by date

  From Date Subject
Next Message Denis Perchine 2000-06-22 06:55:27 Re: libpq error codes
Previous Message Philip J. Warner 2000-06-22 06:31:33 Re: Big 7.1 open items