pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: mahamood hussain <hussain.ieg@gmail.com>
To: Licio Matos <licio.matos@gmail.com>
Cc: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Urgent !!!! Tables inaccessible postgres v17.6
Date: Sat, 15 Aug 2026 00:09:11 +0200
Message-ID: <927e28d9d875aa9f1812c54d12fdffa6ba41f68a.camel@cybertec.at> (raw)
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>

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

> We are using Azure Premium SSD v2, which provides 99.999999999% durability, and my
> understanding is that Azure designed this storage to support configurations 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 PostgreSQL. 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 distribution.

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


Yours,
Laurenz Albe






view thread (15+ messages)

Message-ID: <927e28d9d875aa9f1812c54d12fdffa6ba41f68a.camel@cybertec.at>
Permalink:  ../927e28d9d875aa9f1812c54d12fdffa6ba41f68a.camel@cybertec.at/
Also on:    postgresql.org/message-id/927e28d9d875aa9f1812c54d12fdffa6ba41f68a.camel@cybertec.at

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: laurenz.albe@cybertec.at, hussain.ieg@gmail.com, licio.matos@gmail.com, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Urgent !!!! Tables inaccessible postgres v17.6
  In-Reply-To: <927e28d9d875aa9f1812c54d12fdffa6ba41f68a.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox