| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: First-draft release notes for next week's releases |
| Date: | 2014-03-19 21:09:09 |
| Message-ID: | 532A0775.90607@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/19/2014 02:01 PM, Alvaro Herrera wrote:
> 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.
Would users which this corruption necessarily have broken FKs which
would show up as such on a simple query? That is, if I did:
SELECT ref_id FROM referenced WHERE ref_id NOT IN ( SELECT ref_id FROM
referencing )
... or something similar, would that show the issue?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darren Duncan | 2014-03-19 21:16:48 | Re: [pgsql-advocacy] First draft of update announcement |
| Previous Message | Alvaro Herrera | 2014-03-19 21:01:33 | Re: First-draft release notes for next week's releases |