Re: Alternative database locations are broken

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Cc: Vadim Mikheev <vmikheev(at)sectorbase(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Alternative database locations are broken
Date: 2000-11-06 19:33:55
Message-ID: Pine.LNX.4.21.0011062025320.776-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net http://yi.org/peter-e/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-06 20:08:13 Re: Alternative database locations are broken
Previous Message Peter Eisentraut 2000-11-06 18:58:07 Re: Re: BIT/BIT VARYING status