RE: Disk Groups/Storage Management for a Large Database in PostgreSQL

From: Scot Kreienkamp <Scot(dot)Kreienkamp(at)la-z-boy(dot)com>
To: Amit Sharma <amitpgsql(at)gmail(dot)com>
Cc: Olivier Gautherot <ogautherot(at)gautherot(dot)net>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: RE: Disk Groups/Storage Management for a Large Database in PostgreSQL
Date: 2024-01-23 20:33:32
Message-ID: DM6PR15MB3797537C789B024C0843AFDD9A742@DM6PR15MB3797.namprd15.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks Olivier and Scot for your inputs!

Another data point I would like to share is that VMs will be built in Azure Cloud with Azure Managed Storage and Locally redundant storage (LRS) option with a remote DR as well.

LVM or ZFS would still be a good option to allow easy storage/disk management like add, resize or remove disks while PostgreSQL services are up?
Is equal data distribution a challenge on LVM/ZFS disks?

Thanks
Amit

I would not call data distribution a challenge, but something to be aware of. If LVM has 3 disks in a pool it will, by default, use all of disk 1, then use all of disk 2, then use all of disk 3. The reason for that is with the default you can add new disks one at a time. With striping you must add new disks equal to the number of stripes. Either way I would still advise use of LVM.

Scot Kreienkamp | Applications Infrastructure Architect | La-Z-Boy Corporate
One La-Z-Boy Drive | Monroe, Michigan 48162 | • (734) 384-6403 | | • 1-734-915-1444 | Email: Scot(dot)Kreienkamp(at)la-z-boy(dot)com

This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message James Colannino 2024-01-24 00:55:27 Providers missing from pgdg-common for GDAL 3.7 (related to multiple missing providers from pgdg-common)
Previous Message Francisco Olarte 2024-01-23 20:28:23 Re: Need assistance for running postgresql procedures