Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id D55862E0064 for ; Wed, 18 Jun 2008 13:30:22 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 52371-02 for ; Wed, 18 Jun 2008 13:30:16 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id 9AE252E0051 for ; Wed, 18 Jun 2008 13:30:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m5IGUDUY028496; Wed, 18 Jun 2008 12:30:13 -0400 (EDT) To: wolfgang.graf@ksb.com cc: pgsql-admin@postgresql.org Subject: Re: Move postmater.pid completly In-reply-to: References: Comments: In-reply-to wolfgang.graf@ksb.com message dated "Wed, 18 Jun 2008 12:28:38 +0200" Date: Wed, 18 Jun 2008 12:30:13 -0400 Message-ID: <28495.1213806613@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/141 X-Sequence-Number: 29479 wolfgang.graf@ksb.com writes: > is there a way to move the postmaster.pid file > completely out of the PGDATA directory ? No, and it's unlikely to be seriously considered, because of the enormously increased risk of starting two postmasters in the same directory. All it would take is for them to have different ideas of where the lock file is. > Background: we would like to start a postmaster instance on a readonly > directory to enable a server for readonly operations (SELECT) only. That won't ever work; the pid file is just the tip of the iceberg. regards, tom lane