| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | Dmitry O Litvintsev <litvinse(at)fnal(dot)gov>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: something weird happened - can select by column value although column value exist |
| Date: | 2018-10-11 21:03:08 |
| Message-ID: | 24100.1539291788@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ron <ronljohnsonjr(at)gmail(dot)com> writes:
> On 10/11/2018 03:17 PM, Dmitry O Litvintsev wrote:
>> Today the following happened:
>> < 2018-10-11 13:31:52.587 CDT >ERROR: insert or update on table "file" violates foreign key constraint "$1"
>> < 2018-10-11 13:31:52.587 CDT >DETAIL: Key (volume)=(155303) is not present in table "volume".
>> [ but it is present ]
>>
>> What is this? Version 9.3.9,. running on Linux RH6.
> Index corruption? Maybe rebuild the FK.
Yeah, I'd suspect index corruption as well, particularly seeing that this
is a three-year-old point release in a branch that had more than its share
of data corruption issues. My suggestion is first update to 9.3.latest,
then reindex.
BTW, 9.3.x will be EOL next month, so you should be thinking about getting
onto a later release branch ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ravi Krishna | 2018-10-11 21:08:19 | Re: COPY threads |
| Previous Message | Ron | 2018-10-11 20:23:21 | Re: something weird happened - can select by column value although column value exist |