Skip site navigation (1) Skip section navigation (2)

Re: Re: [GENERAL] Warning: Don't delete those /tmp/.PGSQL.* files

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-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
> >
> 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.


# there should be a way of specifing dbname later too



Also there should be possible to give another configuration file
with env vars or command-line parameters.

Well, just a idea.


In response to


pgsql-hackers by date

Next:From: Don BaccusDate: 2000-11-27 15:18:48
Subject: Re: Re: [NOVICE] Re: re : PHP and persistent connections
Previous:From: Jan WieckDate: 2000-11-27 12:47:32
Subject: Re: Changes to libpgtcl

pgsql-general by date

Next:From: Paul BreenDate: 2000-11-27 14:16:28
Subject: Re: Postgres 7 pgdump problems
Previous:From: Michael AnsleyDate: 2000-11-27 12:47:25
Subject: RE: [HACKERS] Indexing for geographic objects?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group