I'm still getting this duplicate key violation error on the toast
table. I've re-indexed both the main table and the toast table, would
clustering the table, or recreating the table with a select into fix
this problem?
Also, I believe this index is created by the database so I shouldn't be
able to insert data that causes this error, shouldn't the database
complain a little louder about this error?
-mike
Tom Lane wrote:
>Michael Guerin <guerin@rentec.com> writes:
>
>
>>We're starting to get a number of complaints about "duplicate key
>>violations" on a index for one of the toast tables. It started
>>happening after our server was brought down over the weekend, so I
>>suspect postgresql wasn't shutdown properly. Below is the description
>>of the index.
>>
>>
>
>
>
>>I'm doing a re-index on the user table that is associated with the toast
>>table, is this the right thing to do? Is there something else I should do?
>>
>>
>
>I don't think that will touch the toast table --- you should reindex the
>toast table or index explicitly.
>
> regards, tom lane
>
>