Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gfRZ7-0000RI-6P for pgsql-admin@arkaria.postgresql.org; Fri, 04 Jan 2019 15:39:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gfRZ5-0001rk-TT for pgsql-admin@arkaria.postgresql.org; Fri, 04 Jan 2019 15:39:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gfRYk-0007LZ-QP for pgsql-admin@lists.postgresql.org; Fri, 04 Jan 2019 15:38:55 +0000 Received: from mail-wr1-x441.google.com ([2a00:1450:4864:20::441]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gfRYh-0003m9-Oy for pgsql-admin@lists.postgresql.org; Fri, 04 Jan 2019 15:38:53 +0000 Received: by mail-wr1-x441.google.com with SMTP id x10so36916161wrs.8 for ; Fri, 04 Jan 2019 07:38:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=JhcuWJlqQoXsDFfnTfvh0Cnn/k4roaiiF1tz51cfcIM=; b=MwO+JMk9/PMJPZM2q/M+4+QffeyG7q56/LPU40zUM000IsfI+pGSELGVFXFzRUqkk0 7IrX2XvbBdMYN8Ybf3fgngwC1HFOJhEr9dzUsHX7fMArgRQstUr7gEnN/ffXjdFG9LmE X6K88FYfjz/vAOEpLrcVE+NwtgMi+2yohPBnf9+QTGHetpBa4HKIV+XlZ7K+PohnTok5 wbAmCc2Itpg+anIKTneWaCEvou/58oqb4UyGY8F3VyVVZHYo2MVBO09cJTA/rogFr2K1 kl5E3R8TPQmKXQ+4bjD4T6rP2vByyDJulhGlZT75SCXZpiifYO94eujhUSjoY3KjOCQn wRTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=JhcuWJlqQoXsDFfnTfvh0Cnn/k4roaiiF1tz51cfcIM=; b=dsbcj4ussoKFEB4ZwcwOD0NeyJkVW6y187BthVGHfq85COwsugi9vF3F0mF22WjjKl CWN5SrLlVvljX2teFkZUMqoC8yJUSwwTujojm/eCPlJPU5+0MsoBbZqvpJYJXDYtCF6N SsBT5BGzW9fYWdaLQGspilVWj5vjzwm8rx6e/U4axWRFZx2uCXGyStR69H+JP3kdv5hF F429FSwVmfDdIB49oIzIHPqf/kGB7WyWrDZ3GSKqdOLJAs/b1ZlOPl+L0GpvkotZtg5Y hNfHT7xzPlc+VV5MK0yk6NO0iGjxmmrwnwtkthU4bvugU0abcwMECNs7egO+7bsp7pTT vzpQ== X-Gm-Message-State: AJcUukealCAA2MMKFrCzy8PdV1jLAI4UPlHMeWIHPsoiZxMzxl3aCluQ iPdC3SgPjUE0ikU8I/kkPZe4ZQeN X-Google-Smtp-Source: ALg8bN52o/2LTUkWz7vg8FkB++z2cMfJ11zYjHWRzUlJfSQV8E6qplEneHaOfHcnpezkLa4l9ci7vA== X-Received: by 2002:adf:bb44:: with SMTP id x4mr46760011wrg.24.1546616329981; Fri, 04 Jan 2019 07:38:49 -0800 (PST) Received: from [10.1.10.6] ([172.98.67.87]) by smtp.googlemail.com with ESMTPSA id y1sm1418623wme.1.2019.01.04.07.38.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Jan 2019 07:38:49 -0800 (PST) Subject: Re: Multiple postgresql clusters with same version and separate binaries To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: Date: Fri, 4 Jan 2019 09:38:47 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------3FEC16FE54D100CB15EC6926" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------3FEC16FE54D100CB15EC6926 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit If uptime is a priority, then unless they're small, you should think about separating them onto separate servers.  And implementing replication for DR. On 1/4/19 9:30 AM, Erika Knihti-Van Driessche wrote: > Hi, > > Thanks all for your replies and help! I already thought that it’ll be > possible to just install binaries in different locations. My current > installation I have all done using one binary location and initdb.. not a > very good solution on hindsight.. Oh, and I’m on RHEL 7. I used the > installation packages from EDB for Postgres. Previously I did do a minor > upgrade - shutdown all clusters and upgrade, then startup all.. but now > they start doing difficult with downtime for all applications at the same > time, so with next upgrade, I’ll separate all binaries. > > Cheers, > Erika > >> On 4 Jan 2019, at 15:50, Shreeyansh Dba > > wrote: >> >> Hi Erika, >> >> You can create the different version services and use these services for >> PostgreSQL start/stop. >> ex. >> service postgresql-10 start >> service postgresql-9.6 start >> >> Thanks & Regards, >> *Shreeyansh DBA Team* >> www.shreeyansh.com >> >> >> On Fri, Jan 4, 2019 at 7:51 PM Erika Knihti-Van Driessche >> > wrote: >> >> Hi, >> >> I have 10+ postgresql clusters (v 9.6) running on one machine - each >> having their own data directory and port. They all share same >> binaries though, and this is now giving me some headache.. I cannot >> shutdown all clusters at the same time, so upgrading them is quite >> impossible. >> >> I know that running several versions of postgres is possible on one >> machine - I suppose this would also work out with same version >> running on different locations, like /db1/PostgreSQL/10, >> /db2/PostgreSQL/10.. etc..? Has anyone any experience with this kind >> of problem? >> >> All help and ideas appreciated! :-) >> >> Thanks, >> Erika >> > -- Angular momentum makes the world go 'round. --------------3FEC16FE54D100CB15EC6926 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit If uptime is a priority, then unless they're small, you should think about separating them onto separate servers.  And implementing replication for DR.

On 1/4/19 9:30 AM, Erika Knihti-Van Driessche wrote:
Hi,

Thanks all for your replies and help! I already thought that it’ll be possible to just install binaries in different locations. My current installation I have all done using one binary location and initdb.. not a very good solution on hindsight.. Oh, and I’m on RHEL 7. I used the installation packages from EDB for Postgres. Previously I did do a minor upgrade - shutdown all clusters and upgrade, then startup all.. but now they start doing difficult with downtime for all applications at the same time, so with next upgrade, I’ll separate all binaries.

Cheers,
Erika

On 4 Jan 2019, at 15:50, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:

Hi Erika,

You can create the different version services and use these services for PostgreSQL start/stop.
ex.
service postgresql-10 start
service postgresql-9.6 start

Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com


On Fri, Jan 4, 2019 at 7:51 PM Erika Knihti-Van Driessche <erika.knihti@gmail.com> wrote:
Hi,

I have 10+ postgresql clusters (v 9.6) running on one machine - each having their own data directory and port. They all share same binaries though, and this is now giving me some headache.. I cannot shutdown all clusters at the same time, so upgrading them is quite impossible.

I know that running several versions of postgres is possible on one machine - I suppose this would also work out with same version running on different locations, like /db1/PostgreSQL/10, /db2/PostgreSQL/10.. etc..? Has anyone any experience with this kind of problem? 

All help and ideas appreciated! :-)

Thanks,
Erika


--
Angular momentum makes the world go 'round.
--------------3FEC16FE54D100CB15EC6926--