Re: Alternative database locations are broken - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Alternative database locations are broken
Date
Msg-id Pine.LNX.4.21.0011062025320.776-100000@peter.localdomain
Whole thread Raw
In response to Re: Alternative database locations are broken  ("Ross J. Reedstrom" <reedstrm@rice.edu>)
Responses Re: Alternative database locations are broken
List pgsql-hackers
Okay, so we'll do the symlinks.

CREATE DATABASE xxx WITH LOCATION='/else/where';

will clone ('cp -r') template1 in /else/where/base/<id> and create a
symlink to there from $PGDATA/base/<id>.  The '/else/where' location will
be stored in pg_database.datpath.

How do we control the allowed paths?  Should we continue with the
environment variables?  Perhaps a config option listing the allowed
directories?  A system catalog?

Somehow I also get the feeling that pg_dumpall should be saving these
paths...

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: "Martin A. Marques"
Date:
Subject: Re: problems with configure
Next
From: Tom Lane
Date:
Subject: Re: Alternative database locations are broken