| From: | Wes <wespvp(at)syntegra(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Concurrency problem building indexes |
| Date: | 2006-04-25 03:39:44 |
| Message-ID: | C0730430.23AE7%wespvp@syntegra.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
>> 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...
I just verified using 'ps' that there are no other open connections when the
index builds are running. I tried somewhat bigger test tables (a few rows
to a little over a hundred thousand). I can duplicate the error at will.
Wes
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-25 04:02:56 | Re: [GENERAL] Concurrency problem building indexes |
| Previous Message | Christopher Browne | 2006-04-25 03:28:22 | Re: How to have a blind-superuser |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-25 04:02:56 | Re: [GENERAL] Concurrency problem building indexes |
| Previous Message | Tom Lane | 2006-04-25 03:16:08 | Re: TODO Item: ACL_CONNECT |