Re: First-draft release notes for next week's releases

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: First-draft release notes for next week's releases
Date: 2014-03-19 21:01:33
Message-ID: 20140319210132.GM6899@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2014-03-19 21:09:09 Re: First-draft release notes for next week's releases
Previous Message Tom Lane 2014-03-19 20:55:22 Re: First-draft release notes for next week's releases