From: | "Owens, Steve" <Steve(dot)Owens(at)xerox(dot)com> |
---|---|
To: | <psql-general(at)postgresql(dot)org> |
Subject: | Any way to stop PostgreSQL from using Unix domain sockets? |
Date: | 2004-09-22 16:54:52 |
Message-ID: | 309AD90BD8FC7E4383DB1ACCBF6C8DC00320D6@usa0300ms01.na.xerox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ok, here's the situation: we need to be able to spin the server running
PostgreSQL down for power reasons (we have it set for wake on lan, so
we'll still pick up the connections). However, the checkpoint code
breaks out of its select every 5 minutes to do its thing. When it
re-enters the select, it apparently "pings" the unix domain socket file
in /tmp, which causes the disk to spin up, which causes the machine to
wake up from power saver.
I know you can set the checkpoint timeout via postgresql.conf, however
the highest setting is 3600 seconds, which isn't good enough (don't
ask). So, alternately, is there any easy way I can configure PostgreSQL
to TCP exclusively (i.e. no unix domain sockets *at all*)?
Xerox Disclaimer: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential
information. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient(s) please contact the
sender by reply e-mail and destroy all copies of the original message.
Finally, the recipient should check that this email is authentic and
examine it for the presence of viruses. Xerox does perform virus checks
but cannot accept liability for any damage caused by any virus
transmitted by this email. Thank you.
From | Date | Subject | |
---|---|---|---|
Next Message | Pierre-Frédéric Caillaud | 2004-09-22 17:06:29 | Re: gist index woes |
Previous Message | Boris Folgmann | 2004-09-22 16:00:10 | Re: Trouble with query logging |