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

Поиск
Список
Период
Сортировка
От Josh Berkus
Тема Re: First-draft release notes for next week's releases
Дата
Msg-id 532A0775.90607@agliodbs.com
обсуждение исходный текст
Ответ на 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>)
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jeff Janes
Дата:
Сообщение: effective_cache_size cannot be changed by a reload
Следующее
От: Darren Duncan
Дата:
Сообщение: Re: [pgsql-advocacy] First draft of update announcement