| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Wes <wespvp(at)syntegra(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Concurrency problem building indexes |
| Date: | 2006-04-25 00:54:47 |
| Message-ID: | 20060425005446.GT64695@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, Apr 24, 2006 at 08:42:41PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> > Was the code ever changed so that it won't update relpages if the number
> > is the same?
>
> Long ago. I just tested it again, and AFAICS you can create indexes
> concurrently so long as the underlying table isn't changing (ie,
> neither reltuples nor relpages changes).
Hrm, the OP seemed to find a case that was having problems:
http://archives.postgresql.org/pgsql-general/2006-04/msg01009.php
Of course it's possible that he's getting that error from an entirely
different section of code, or that this is now only an issue if you're
doing a lot of indexing at once...
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David F. Johnson | 2006-04-25 01:20:19 | Re: "save history" problem |
| Previous Message | Tom Lane | 2006-04-25 00:42:41 | Re: [GENERAL] Concurrency problem building indexes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gevik Babakhani | 2006-04-25 01:12:28 | Re: TODO Item: ACL_CONNECT |
| Previous Message | Tom Lane | 2006-04-25 00:42:41 | Re: [GENERAL] Concurrency problem building indexes |