Re: PostgreSQL 'Corruption & Fragmentation' detection andresolution/fix - Mailing list pgsql-admin

From Rui DeSousa
Subject Re: PostgreSQL 'Corruption & Fragmentation' detection andresolution/fix
Date
Msg-id 957A97A0-73D7-4F53-B34A-E086AEC80596@icloud.com
Whole thread Raw
In response to Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix
List pgsql-admin

> On Jun 12, 2018, at 12:16 PM, Peter Geoghegan <pg@bowt.ie> wrote:
>
> On Tue, Jun 12, 2018 at 8:21 AM, Rui DeSousa <rui.desousa@icloud.com> wrote:
>> Note that DBCC was never a selling point and neither is fsck; the fact that those tools are needed is a problem.
>
> DBCC is a selling point. "Parallel consistency check" is a feature
> that is only available in SQL Server enterprise edition.

That’s not what I recall; it was clearly used against it in sales pitches.  Do you really want to trust a database that
requiresyou to DBCC checkdb periodically and fix corruption data pages or do you want to trust Oracle with data? 

Would you use a filesystem today that required you to fsck after a crash?

Sure DBCC has useful features like tracing, etc. — it’s not just for corruption.



pgsql-admin by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix
Next
From: Peter Geoghegan
Date:
Subject: Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix