Message-ID: <927e28d9d875aa9f1812c54d12fdffa6ba41f68a.camel@cybertec.at>
Subject: Re: Urgent !!!! Tables inaccessible postgres v17.6
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: mahamood hussain <hussain.ieg@gmail.com>, Licio Matos
	 <licio.matos@gmail.com>
Cc: Ron Johnson <ronljohnsonjr@gmail.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Sat, 15 Aug 2026 00:09:11 +0200
In-Reply-To: 
 <CAGc_7HmOp44pmt5zaS01vP7iSHS08tN6SWh1g-NH3HTg3k9A=g@mail.gmail.com>
References: 
	<CAGc_7Hmr9zd039d-K1q9s81iyw06uFPdaskxtts_OsKvVD23dQ@mail.gmail.com>
	 <CANzqJaDLNoD+1QPpkMR4kd9zAHhg5hny+O_yHpW1T++Rf4Ku9Q@mail.gmail.com>
	 <CAGc_7HnWpuTQS3_W6Ysuy-_gZs2YH3q7C=d0rebezogSg5doZw@mail.gmail.com>
	 <a23d113b7f13b4450d8a2a6a5765e6e576aafdf0.camel@cybertec.at>
	 <CAK6Tc4Op4=pD2ZL2AS789j+=Tx7MbRnzBzFf7BBWFrmeC+Cw0A@mail.gmail.com>
	 <CAGc_7H=2dSUP93B4hf21mDHbY-_U8AjHwQ0jiFbwcvcQaYS6JQ@mail.gmail.com>
	 <CAK6Tc4MMjL0fPoT6zQFVBUZzno+jZ4_EM3Z2o9SbLXGHrxaM7g@mail.gmail.com>
	 <CAGc_7HmOp44pmt5zaS01vP7iSHS08tN6SWh1g-NH3HTg3k9A=g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.60.2 (3.60.2-1.fc44) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/927e28d9d875aa9f1812c54d12fdffa6ba41f68a.camel%40cybertec.at>
Precedence: bulk

On Thu, 2026-08-13 at 14:25 +0530, mahamood hussain wrote:

> We are using Azure Premium SSD v2, which provides 99.999999999% durabilit=
y, and my
> understanding is that Azure designed this storage to support configuratio=
ns such as
> RAID 0 when higher IOPS/throughput are required.

I don't know how "durability" is defined there.
You got corruption, so either that's durable corruption or you are in the 0=
.000000001%.


> For context, these databases were recently migrated from DB2 to PostgreSQ=
L. In DB2,
> we have the concept of storage groups and storage paths, which allows us =
to place
> tablespaces across multiple disks/storage paths for performance and I/O d=
istribution.

If you control the storage, nothing keeps you from creating your data direc=
tory
in a file system that is striped across multiple devices to achieve the sam=
e thing.
But in a virtualized environment, that's pretty moot: it all ends up on the=
 same
storage anyway.


Yours,
Laurenz Albe