Re: Big 7.1 open items

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 02:29:42
Message-ID: 200006220229.WAA08130@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> Bruce Momjian wrote:
>
> > The symlink solution where the actual symlink location is not stored
> > in the database is certainly abstract. We store that info in the file
> > system, which is where it belongs. We only query the symlink location
> > when we need it for database location dumping.
>
> how would that work? would pg_dump dump the tablespace locations or not?
>

pg_dump would recreate a CREATE TABLESPACE command:

printf("CREATE TABLESPACE %s USING %s", loc, symloc);

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.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-06-22 03:01:16 Re: An idea on faster CHAR field indexing
Previous Message Randall Parker 2000-06-22 01:52:34 Re: Thoughts on multiple simultaneous code page support

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2000-06-22 03:27:10 Re: Big 7.1 open items
Previous Message Hiroshi Inoue 2000-06-22 01:15:01 RE: Big 7.1 open items