Re: First-draft release notes for next week's releases - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: First-draft release notes for next week's releases
Date
Msg-id 532A0321.4040400@agliodbs.com
Whole thread Raw
In response to First-draft release notes for next week's releases  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: First-draft release notes for next week's releases  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: First-draft release notes for next week's releases  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
All,

So, I'll ask again (because I didn't see a reply): is there any way
users can *check* if they've been corrupted?  Short of waiting for PK/FK
violations?

Given that all of the fixes we recommend involve extensive downtimes,
nobody is going to want to do them "just in case".  How can they test
for the issue?  I can't see any reasonable way ...

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Wiki Page Draft for upcoming release
Next
From: Josh Berkus
Date:
Subject: Re: First draft of update announcement