Thread: Moving lock file (/tmp/.s.PGSQL.)

Hi all,

   If there a ./configure switch (or config file/command line switch) to
tell postgresql to put the lock file '.s.PGSQL.<port>.lock' and socket
'.s.PGSQL.<port>' in a different directory?

Thanks all!

Madi

am  Fri, dem 30.11.2007, um  5:22:34 -0500 mailte Madison Kelly folgendes:
> Hi all,
>
>   If there a ./configure switch (or config file/command line switch) to
> tell postgresql to put the lock file '.s.PGSQL.<port>.lock' and socket
> '.s.PGSQL.<port>' in a different directory?
>
> Thanks all!

Option unix_socket_directory in file postgresql.conf.



Andreas
--
Andreas Kretschmer
Kontakt:  Heynitz: 035242/47150,   D1: 0160/7141639 (mehr: -> Header)
GnuPG-ID:   0x3FFF606C, privat 0x7F4584DA   http://wwwkeys.de.pgp.net

On Fri, 30 Nov 2007, Madison Kelly wrote:

>   If there a ./configure switch (or config file/command line switch) to
> tell postgresql to put the lock file '.s.PGSQL.<port>.lock' and socket
> '.s.PGSQL.<port>' in a different directory?

There's no ./configure option, so you should change
    DEFAULT_PGSOCKET_DIR in ./src/include/pg_config_manual.h
If every client is linked (preferably dynamically) with libpq, which
is compiled with changed DEFAULT_PGSOCKET_DIR, then this would work
with no special configuration.

Alternatively there's a command line switch "-k" or
"unix_socket_directory" config option for postgres server:
http://www.postgresql.org/docs/8.2/interactive/runtime-config-connection.html

And PGHOST environment variable for clients:
http://www.postgresql.org/docs/8.2/interactive/libpq-envars.html

Regards
Tometzky
--
...although Eating Honey was a very good thing to do, there was a
moment just before you began to eat it which was better than when you
were...
                                                      Winnie the Pooh