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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Ryan Mahoney <ryan(dot)mahoney(at)outlook(dot)com>
Cc: "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:19:02
Message-ID: CAKFQuwZQ6moO7ZydhvvyOBNPw6=FUtM9eNaac6eCat++eOHAyQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Nov 8, 2016 at 12:48 PM, Ryan Mahoney <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 Adrian Klaver 2016-11-08 20:20:09 Re: resolution order for foreign key actions?
Previous Message Moreno Andreo 2016-11-08 20:13:52 Best practices to manage custom statistics