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.g.johnston@xxxxxxxxx>
Sent: Tuesday, November 8, 2016 3:19:02 PM
To: Ryan Mahoney
Cc: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: Running on Docker, AWS with Data Stored on EBS
Sent: Tuesday, November 8, 2016 3:19:02 PM
To: Ryan Mahoney
Cc: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: Running on Docker, AWS with Data Stored on EBS
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.
