Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r8k8Q-00BRGc-Pb for pgsql-general@arkaria.postgresql.org; Thu, 30 Nov 2023 16:43:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r8k8P-001PIE-2k for pgsql-general@arkaria.postgresql.org; Thu, 30 Nov 2023 16:43:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r8k8O-001PI6-OA for pgsql-general@lists.postgresql.org; Thu, 30 Nov 2023 16:43:28 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r8k8M-009Nll-GV for pgsql-general@postgresql.org; Thu, 30 Nov 2023 16:43:28 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailout.nyi.internal (Postfix) with ESMTP id 68AA85C028A; Thu, 30 Nov 2023 11:43:25 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 30 Nov 2023 11:43:25 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1701362605; x=1701449005; bh=3hJz39C+6t9MYHyPw/Rvvu7Sg+nfASIckcn b9iEW9QA=; b=h7PCPZZIrnAuYH8p/P9CoWaHTETz7hqwe1urIMhgTVs8KJ4S02V e3jYCUOH3Ouu+SKk4z01TO38gVuXoM+G9aM7uMuwwd30fAnfCwjOSz6S0VrEPOys W0sGsqwirEUqPAlZfRbwNdzJmwTlZIDGI2qZmHmKocqK9cv1oW0dRjuRCED19FwO RK5CSM7PRpnxJUQqvUqfJ2Ino+Qx2tcZhvNVvdBhVhlq3XtibG81aJqil0Y51f/S VdithXy1yFnhwxWIas3Euy7AiIG07A4MijJVYPZYQUY8qzD+17rio4t2nfD+xmcu VHapI7O4IpYtzqEFdMGfUbxxNp8g6miYYlw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1701362605; x= 1701449005; bh=3hJz39C+6t9MYHyPw/Rvvu7Sg+nfASIckcnb9iEW9QA=; b=D EGuBqiwA0ZpVnOqjgW5KNmO3K2wz8wBk4mgbzlrjK5B5snPSgNh6bclRjnkR0WRy 30wsdOiRD1wDz/5NuoF1aeEZ4eXu/StkfSQ7dBxnq39Nq4MKjh+R0hQenhho6zPe irhHHzafPXGSznw3l/oAhnVoLJ75PjJLclKVx+IJKndhjzIhIJ+VapKkB3pIgrB5 066sJrN/ZWJmaCKjr5rqNQniOT15JPbD5DNOezi/a5vBmq6jkync67RtqyBGM0jO 9m0bwEmX1wX8nv5kxy2pe217jtDblvUJgAj1l2Z4a1acHq6vzL+2UAfn3j6xuhF2 K9l+z8B8m4OAodvuwedLg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudeijedgleduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhk lhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepffelgeeife fgveduhedthfekuedtffejveegffegjeevtdehgfduieetfeehjeehnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvh gvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 30 Nov 2023 11:43:24 -0500 (EST) Message-ID: Date: Thu, 30 Nov 2023 08:43:24 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Two started cluster on the same data directory and port Content-Language: en-US To: Loles , PostgreSQL References: <477f32ab-72cc-4888-835a-0f25aa3db705@aklaver.com> From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/30/23 08:37, Loles wrote: > Every time I stop the main_old cluster with sudo pg_ctlcluster stop 14 > main_old, both are stopped. And when I raise sudo pg_ctlcluster start 14 > main, both are raised. > > I don't know how I got into this situation and I don't know how to > resolve it. Is there both?: /etc/postgresql/14/main/ /etc/postgresql/14/main_old/ > > > El jue, 30 nov 2023 a las 17:34, Loles ( >) escribió: > > Indeed, that is the problem, they are two different clusters, > pointing to the same data directory and reading from the same port. > > I can't change the port because it is the same postgresql.conf > > I don't know how to disassociate the main_old cluster from the data > directory or how to resolve this situation. > > El jue, 30 nov 2023 a las 16:32, Adrian Klaver > (>) > escribió: > > On 11/30/23 07:23, Adrian Klaver wrote: > > On 11/30/23 05:37, Loles wrote: > >> Hi! > >> > >> I have this situation on a server that is giving me problems. > >> > >> postgres@hostname:~$ pg_lsclusters > >> Ver Cluster  Port Status Owner    Data directory >  Log file > >> 14  main     5432 online postgres /var/lib/postgresql/14/main > >> /var/log/postgresql/postgresql-14-main.log > >> 14  main_old 5432 online postgres /var/lib/postgresql/14/main > >> /var/log/postgresql/postgresql-14-main_old.log > >> > >> How can I stop, even delete, the main_old cluster? > > > > Assuming you are on  Debian/Ubuntu. > > > > 1) sudo pg_ctlcluster stop 14 main_old > > > >      This will stop the server for this session > > > > 2) sudo vi  /etc/postgresql/14/main_old/start.conf > > > >      Change auto to manual. > >      This will keep the server from restarting on reboot. > >      You can still start it using > >       sudo pg_ctlcluster start 14 main_old > >      Though if you want to do that then: > >          vi /etc/postgresql/14/main_old/postgresql.conf > >       and change port to something other then 5432. > > > > 3) If you have determined you really don't need that server > and have all > > the data safely backed up or moved to the other server, > then(THIS IS NOT > > REVERSIBLE): > > > >      sudo pg_dropcluster 14 main_old > > Blaming it on not enough coffee, but I just noticed both > clusters are > pointing at the same data directory. I would NOT do: > >      sudo pg_dropcluster 14 main_old > > > > >> > >> Thanks! > >> > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > -- Adrian Klaver adrian.klaver@aklaver.com