| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Insert query hangs |
| Date: | 2014-07-09 11:12:29 |
| Message-ID: | CAM-w4HPREK-JvotFMzPiPMuPOD2tVp368LnCHNSa53wNr2Ld8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Wed, Jul 9, 2014 at 11:34 AM, M Tarkeshwar Rao
<m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com> wrote:
>
> We analysed one more thing when we removed the unique index from the table it is working fine.
> Is there any issue in indexing?
>
> Is there any option to repair the table or its indexing?
REINDEX is useful for indexes.
From the sounds of it you had an uncommitted transaction that had
inserted a conflicting id. If you were able to drop the index the
other transaction had committed (or aborted) by that time.
It's possible there was corruption but that doesn't usually lead to a
hang and you haven't provided enough information to think that was the
case.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Moran | 2014-07-09 11:14:32 | Re: php password authentication failed for user ... |
| Previous Message | basti | 2014-07-09 11:04:19 | php password authentication failed for user ... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-07-09 12:06:21 | Re: psql: show only failed queries |
| Previous Message | Jeevan Chalke | 2014-07-09 11:02:29 | Re: Allowing NOT IN to use ANTI joins |