X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8BE5ED1D2BC for ; Thu, 11 Mar 2004 14:53:32 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 84369-03 for ; Thu, 11 Mar 2004 10:53:28 -0400 (AST) Received: from ucsns.ucs.co.za (ucs.co.za [196.23.43.2]) by svr1.postgresql.org (Postfix) with ESMTP id E0706D1DBD8 for ; Thu, 11 Mar 2004 10:53:23 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by ucsns.ucs.co.za (Postfix) with ESMTP id DE0D82BDB4 for ; Thu, 11 Mar 2004 16:53:25 +0200 (SAST) Received: from ucsns.ucs.co.za ([127.0.0.1]) by localhost (ucsns.ucs.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02628-03 for ; Thu, 11 Mar 2004 16:53:02 +0200 (SAST) Received: from ucspost.ucs.co.za (mailgw1.ucs.co.za [196.23.43.253]) by ucsns.ucs.co.za (Postfix) with ESMTP id 9519D2BDC1 for ; Thu, 11 Mar 2004 16:53:02 +0200 (SAST) Received: from jhb.ucs.co.za (jhb.ucs.co.za [172.31.1.3]) by ucspost.ucs.co.za (Postfix) with ESMTP id 57A45D9EE0 for ; Thu, 11 Mar 2004 16:53:02 +0200 (SAST) Received: from svb.ucs.co.za (svb.ucs.co.za [172.31.1.148]) by jhb.ucs.co.za (Postfix) with SMTP id 50F4497685 for ; Thu, 11 Mar 2004 16:53:02 +0200 (SAST) Date: Thu, 11 Mar 2004 16:52:56 +0200 From: Stef To: pgsql-admin@postgresql.org Subject: Multiple postmasters for one data directory... Message-Id: <20040311165256.5a68e02a.svb@ucs.co.za> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) User-Agent: sillypheed-claws (anti-aliased) X-Face: GFoC95e6r)_TTG>n~=uFLojP=O~4W@Ms]>:.DMm/')(z3\Mwj^XP@? Q:3";lD.OM1"^mDu}2NJ@US:)dO:U*iY5EM50&Tx. X-Operating-System: sid X-X-X: _-^-_ Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Thu__11_Mar_2004_16_52_57_+0200_EC0vMT1hs9FSCkKs" X-Virus-Scanned: by amavisd-new at ucs.co.za X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/199 X-Sequence-Number: 12768 --Signature=_Thu__11_Mar_2004_16_52_57_+0200_EC0vMT1hs9FSCkKs Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Hi all, I've got a situation on certain machines where approximately 70 postmasters are running. Each with one database, and one data directory. This is fine most of the time, except for a certain time of the month, when a very large consolidation process has to run on each database. At this time it is impossible to have all databases started with more shared memory, and I basically lose the benefits of using a cluster that can make use of much more memory at a time. I've managed to make such a database cluster on a separate postmaster, and re-linked all the database directories to point to the data directories of all the other postmasters. Although this workaround seems to be working rather well, I know for one thing that it could be disastrous to have two postmasters running on the same data directory at the same time, so I'll ensure that that doesn't happen. Is what I'm doing VERY bad, and are there more things I'm overlooking? Can this setup possibly break everything? Kind Regards Stefan --Signature=_Thu__11_Mar_2004_16_52_57_+0200_EC0vMT1hs9FSCkKs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQCVAwUBQFB9TroLc+HYd7LFAQJcMQP/VGCjQ4eeX1igiyBOxGSmWK4h8UwFRxuv Ip+MkdyF5RyVLgPwP0V+UsLlBZi30XNdKf+j8A23sz+cOMIlWXcrbCSgZX0iRZeg +FNH6XK74K/ajWq5UOsV86Nju0WovCMeFCbAjpgy2U0T+flUMVvxeCpVDQyfWqA6 eQgeydAXMFo= =oX6q -----END PGP SIGNATURE----- --Signature=_Thu__11_Mar_2004_16_52_57_+0200_EC0vMT1hs9FSCkKs--