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.
El jue, 30 nov 2023 a las 17:34, Loles (<lolesft@gmail.com>) 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.
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:
