Drive Architecture for new PostgreSQL Environment

From: "Hilbert, Karin" <ioh1(at)psu(dot)edu>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Drive Architecture for new PostgreSQL Environment
Date: 2019-06-10 16:35:13
Message-ID: DM6PR02MB487649F792A6EE35808C4D6C89130@DM6PR02MB4876.namprd02.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Kretschmer 2019-06-10 16:51:05 Re: Drive Architecture for new PostgreSQL Environment
Previous Message Igor Korot 2019-06-10 16:30:42 Re: Inserting into the blob