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 81909D1C7F7 for ; Tue, 10 Feb 2004 13:18:09 +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 60379-09 for ; Tue, 10 Feb 2004 09:18:03 -0400 (AST) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id A7A7CD1B4DA for ; Tue, 10 Feb 2004 09:17:58 -0400 (AST) Received: (qmail 32085 invoked by uid 500); 10 Feb 2004 13:19:46 -0000 Date: Tue, 10 Feb 2004 07:19:46 -0600 From: Bruno Wolff III To: Rodrigo Sakai Cc: pgsql-admin@postgresql.org Subject: Re: Diferent Instances Message-ID: <20040210131946.GB24722@wolff.to> Mail-Followup-To: Rodrigo Sakai , pgsql-admin@postgresql.org References: <20040210121342.16561.qmail@hm10.locaweb.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040210121342.16561.qmail@hm10.locaweb.com.br> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/129 X-Sequence-Number: 12303 On Tue, Feb 10, 2004 at 10:13:42 -0200, Rodrigo Sakai wrote: > > We are using PostgreSQL for a lot of distinct databases, and so the problem is, when occurs an error on just one database and we have to restart the postmaster process, it kills all the others databases that do not have problem, because there is only one instance controling the databases. But we are making an ASP, so we should not run into this kind of problem. > I think abut a solution, if I make initdb for each database, instaling it inside a new folder, like initdb -D /postgresql/datadb1/ ........... > initdb -D /postgresql/datadb2/ and so on....! Then i think I can initialize each database one by one, and in the same way stop and restart them. > Is it a good idea or not??? Is there a better way to do what I want ??? What kind of errors are occurring that require restarting postgres to clear? You probably want to avoid running each database with a separate postmaster.