tag 606336 moreinfo thanks Hello Jens,
sorry for the very late reply! Jens Wilke [2010-12-08 15:28 +0100]: > pg_createcluster creates a cluster on port 5432, even if there's > already another cluster on this port which is down. Do you have a recipe for reproducing this? pg_createcluster doesn't actually poke the ports, it reads the port from postgresql.conf for all clusters and figures out the next free one (see next_free_port() in PgCommon.pm). > pg_lscluster lists both of these clusters as online, if one of them is online. Right, that would happen in this case. You sent a patch for this in a private mail which checks the PID file instead. I think I'll combine these two: If postgresql.conf specifies a PID file, it uses this, otherwise it falls back to cluster_port_running(). Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
