| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Big 7.1 open items |
| Date: | 2000-06-22 04:03:27 |
| Message-ID: | 200006220403.AAA15648@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> > 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-22 04:29:42 | Re: Big 7.1 open items |
| Previous Message | Tatsuo Ishii | 2000-06-22 03:51:02 | Re: Thoughts on multiple simultaneous code page support |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-22 04:29:42 | Re: Big 7.1 open items |
| Previous Message | Chris Bitmead | 2000-06-22 03:43:56 | Re: Big 7.1 open items |