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

Поиск
Список
Период
Сортировка
От Ryan Mahoney
Тема Re: Running on Docker, AWS with Data Stored on EBS
Дата
Msg-id BN6PR20MB12524881E029DEE9982C6ECD8FA60@BN6PR20MB1252.namprd20.prod.outlook.com
обсуждение исходный текст
Ответ на Re: Running on Docker, AWS with Data Stored on EBS  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список 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.g.johnston@gmail.com>
Sent: Tuesday, November 8, 2016 3:19:02 PM
To: Ryan Mahoney
Cc: pgsql-general@postgresql.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.mahoney@outlook.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.

В списке pgsql-general по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: Running on Docker, AWS with Data Stored on EBS
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Gin indexes on intarray is fast when value in array does not exists, and slow, when value exists