From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Andy Colson <andy(at)squeakycode(dot)net>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Tim Mickelson <tim_mickelson(at)bigfoot(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Really strange foreign key constraint problem blocking delete |
Date: | 2014-10-06 22:15:08 |
Message-ID: | 5433146C.6010302@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/5/14, 10:06 AM, Andy Colson wrote:
> On 10/05/2014 10:00 AM, Adrian Klaver wrote:
>> On 10/05/2014 07:37 AM, Tim Mickelson wrote:
>>> Sorry about that, the precise version is: "PostgreSQL 9.1.9 on
>>> x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat
>>> 4.4.7-3), 64-bit"
>>
>> Well 9.1 is at .14 now, so on general principles it would be a good idea to upgrade. That being said I do not see anything in the release notes from .10 to .14 that applies. Though to be truthful I did not read every line. Before upgrading you could try what Andy suggested which is to REINDEX(tmpautenticazione). See here for the REINDEX caveats, and a way to INDEX CONCURRENTLY:
>>
>> http://www.postgresql.org/docs/9.1/interactive/sql-reindex.html
>>
>>>
>>>
>
> I thought .11 sounded like a good candidate. Especially the part:
>
> allowing tuples to escape freezing, causing those rows to become invisible once 2^31 transactions have elapsed
Those rows should then be invisible to the FK checks as well, so I don't think that's it.
My guess is also on a corrupted index. A quick test would be to disable index scans and try the delete again (use EXPLAIN ANALYZE to make sure the delete is using a sequential scan). If that doesn't work, post EXPLAIN ANALYZE output for the commands you're running that generate this error.
--
Jim Nasby, Data Architect, Blue Treble
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2014-10-06 22:18:13 | Re: Converting char to varchar automatically |
Previous Message | Jim Nasby | 2014-10-06 22:08:41 | Re: <idle> question |