Re: Big 7.1 open items - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Big 7.1 open items
Date
Msg-id 200006220229.WAA08130@candle.pha.pa.us
Whole thread Raw
In response to Re: Big 7.1 open items  (Chris Bitmead <chrisb@nimrod.itg.telstra.com.au>)
List pgsql-hackers
> 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@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
 


pgsql-hackers by date:

Previous
From: "Randall Parker"
Date:
Subject: Re: Thoughts on multiple simultaneous code page support
Next
From: Tom Lane
Date:
Subject: Re: An idea on faster CHAR field indexing