From: | Marko Kreen <marko(at)l-t(dot)ee> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [GENERAL] Warning: Don't delete those /tmp/.PGSQL.* files |
Date: | 2000-11-27 13:21:17 |
Message-ID: | 20001127152117.A20875@l-t.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Sat, Nov 25, 2000 at 07:41:52PM -0500, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Actually, this turns out to be similar to what you wrote in
> > http://www.postgresql.org/mhonarc/pgsql-hackers/1998-08/msg00835.html
>
> Well, we've talked before about moving the socket files to someplace
> safer than /tmp. The problem is to find another place that's not
> platform-dependent --- else you've got a major configuration headache.
Could this be described in e.g. /etc/postgresql/pg_client.conf?
a la the dbname idea?
I cant remember the exact terminology, but there is a
configuration file for clients, set at compile time where are
set the connection params for clients.
---------
[db_foo]
type=inet
host=srv3.devel.net
port=1234
# there should be a way of specifing dbname later too
database=asdf
[db_baz]
type=unix
socket=/var/lib/postgres/comm/db_baz
--------
Also there should be possible to give another configuration file
with env vars or command-line parameters.
Well, just a idea.
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Breen | 2000-11-27 14:16:28 | Re: Postgres 7 pgdump problems |
Previous Message | Michael Ansley | 2000-11-27 12:47:25 | RE: [HACKERS] Indexing for geographic objects? |
From | Date | Subject | |
---|---|---|---|
Next Message | Don Baccus | 2000-11-27 15:18:48 | Re: Re: [NOVICE] Re: re : PHP and persistent connections |
Previous Message | Jan Wieck | 2000-11-27 12:47:32 | Re: Changes to libpgtcl |