Drive Architecture for new PostgreSQL Environment

Поиск
Список
Период
Сортировка
От Hilbert, Karin
Тема Drive Architecture for new PostgreSQL Environment
Дата
Msg-id DM6PR02MB487649F792A6EE35808C4D6C89130@DM6PR02MB4876.namprd02.prod.outlook.com
обсуждение исходный текст
Ответы Re: Drive Architecture for new PostgreSQL Environment  (Andreas Kretschmer <andreas@a-kretschmer.de>)
RE: Drive Architecture for new PostgreSQL Environment  (Kevin Brannen <KBrannen@efji.com>)
Список pgsql-general

Hello,


We're in the process of building a new PostgreSQL environment on Scientific Linux release 7.6.

The new environment will have a Primary & 2 Standby servers & have asynchronous replication.  It will use repmgr to manage failover/switchover events.


In the past, we've always had separate separate physical drives for data, pg_xlog & backups.

We did this as a precaution against disk failure.  If we lose one, we would still have the other two to recover from.

Is that really necessary anymore, with having a repmgr cluster?


My Linux Admin wants to do the following instead:

What I propose is to set this up as a single drive and isolate the three directories using the Linux logical volume manager.  As a result, each directory would be on a separate filesystem.  This would provide the isolation that you require but would give me the ability to modify the sizes of the volumes should you run out of space.  Also, since this is a VM and all drives are essentially “virtual”, the performance of this different drive structure would be essentially identical to one with three separate drives.


Your thoughts would be appreciated.

Regards,

Karin Hilbert

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

Предыдущее
От: Igor Korot
Дата:
Сообщение: Re: Inserting into the blob
Следующее
От: Andreas Kretschmer
Дата:
Сообщение: Re: Drive Architecture for new PostgreSQL Environment