Re: Running on Docker, AWS with Data Stored on EBS

From: Ryan Mahoney <ryan(dot)mahoney(at)outlook(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Running on Docker, AWS with Data Stored on EBS
Date: 2016-11-08 20:41:44
Message-ID: BN6PR20MB12524881E029DEE9982C6ECD8FA60@BN6PR20MB1252.namprd20.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for your prompt response.

I'm so glad the use-case will work -- and sounds somewhat normative.

It also looks like the PostgreSQL memory footprint is quite small... so even using the smallest type of EC2 instance is viable (assuming the utilization and data size remain small).

With Appreciation,

Ryan

________________________________
From: David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Sent: Tuesday, November 8, 2016 3:19:02 PM
To: Ryan Mahoney
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Running on Docker, AWS with Data Stored on EBS

On Tue, Nov 8, 2016 at 12:48 PM, Ryan Mahoney <ryan(dot)mahoney(at)outlook(dot)com<mailto:ryan(dot)mahoney(at)outlook(dot)com>> wrote:

Hi All,

TL;TR: Can a new PostgreSQL process, running on a different server instance effectively resume operations by reading the same data directory location as another PostgreSQL process that is no longer running?

In short - yes.

Avoiding concurrent access and ensuring that the various PostgreSQL binaries involved are all running at minimum the same major (9.6.x) version of PostgreSQL, and ideally the same configuration, is what matters.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2016-11-08 20:48:29 Re: Running on Docker, AWS with Data Stored on EBS
Previous Message Adrian Klaver 2016-11-08 20:28:00 Re: Best practices to manage custom statistics