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

From Alvaro Herrera
Subject Re: First-draft release notes for next week's releases
Date
Msg-id 20140319210132.GM6899@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: First-draft release notes for next week's releases  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus wrote:
> 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?

Obviously there are queries you can run to check each FK -- the same
queries that ri_triggers.c would run when you create an FK.  It's
cumbersome to write, but not impossible.  In fact, it can be done
mechanically.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: First-draft release notes for next week's releases
Next
From: Jeff Janes
Date:
Subject: effective_cache_size cannot be changed by a reload