From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Mark Cave-Ayland <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk> |
Subject: | Re: Locating sharedir in PostgreSQL on Windows |
Date: | 2007-11-26 20:15:27 |
Message-ID: | 200711262115.28461.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Am Montag, 26. November 2007 schrieb Mark Cave-Ayland:
> >> I'm working on a piece of code for PostGIS to allow the loading of
> >> projection configuration files from the share/postgresql directory, but
> >
> > The share directory is the wrong place for configuration files anyway.
> > And moreover, non-PostgreSQL packages have no business putting files into
> > PostgreSQL's private directories.
>
> That doesn't seem logical to me. We expect tsearch configuration files
> to be put into $sharedir/tsearch_data, so why shouldn't PostGIS use a
> similar approach to dealing with external configuration data?
Well, PostGIS is not PostgreSQL. And those files are not really configuration
files, in the sense that the user configures them, but data files (or else
they are in the wrong place).
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Bernd Helmle | 2007-11-26 20:41:33 | Re: maintenance_work_mem memory constraint? |
Previous Message | Peter Eisentraut | 2007-11-26 20:14:25 | Re: Locating sharedir in PostgreSQL on Windows |