Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id A0F359FB291 for ; Tue, 17 Apr 2007 14:23:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 56076-03 for ; Tue, 17 Apr 2007 14:23:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A94DA9FB1BD for ; Tue, 17 Apr 2007 14:23:50 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l3HHNn28002899; Tue, 17 Apr 2007 13:23:50 -0400 (EDT) To: Nicola Mauri cc: pgsql-admin@postgresql.org Subject: Re: Lock file conflict with multiple postmasters In-reply-to: References: Comments: In-reply-to Nicola Mauri message dated "Tue, 17 Apr 2007 18:26:16 +0200" Date: Tue, 17 Apr 2007 13:23:49 -0400 Message-ID: <2898.1176830629@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/156 X-Sequence-Number: 25220 Nicola Mauri writes: > In order to avoid this conflict, how can we configure the name of > lockfiles or directory where they are placed? unix_socket_directory regards, tom lane