| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Wes <wespvp(at)syntegra(dot)com> |
| Cc: | Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Concurrency problem building indexes |
| Date: | 2006-05-11 02:25:14 |
| Message-ID: | 28643.1147314314@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I forgot to mention it in the commit message, but this patch
http://archives.postgresql.org/pgsql-committers/2006-05/msg00069.php
includes a fix to avoid "tuple concurrently updated" failures in
CREATE INDEX's update of the parent relation's pg_class entry.
I'm still not convinced that that's where your problem is, however,
because AFAICS that ought to be a pretty low-probability scenario.
If that fixes it for you then there's something pushing the system
to complete index builds at about the same time, and I don't see
what that would be.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2006-05-11 02:43:32 | Re: BEGIN inside transaction should be an error |
| Previous Message | Qingqing Zhou | 2006-05-11 01:57:27 | Re: [HACKERS] Question on win32 semaphore simulation |