| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannes Dorbath <light(at)theendofthetunnel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Index trouble with 8.3b4 |
| Date: | 2008-01-14 00:15:21 |
| Message-ID: | 10977.1200269721@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Hannes Dorbath <light(at)theendofthetunnel(dot)de> writes:
> I have the bad feeling that I need to correct this into "It happens when
> autovacuum is active on the table".
Ah-hah, I realize how to explain that too, now. If you start the CREATE
INDEX CONCURRENTLY while an autovacuum is in progress on that table, the
autovacuum gets booted off so that C.I.C. can get the lock. And, most
likely, it leaves the syncscan pointer positioned someplace past block
zero. So the part that is a bit hard to reproduce is to launch the
C.I.C. while an autovacuum is in progress.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-14 00:22:24 | Re: tsearch2 install on Fedora Core 5 problems |
| Previous Message | Tom Lane | 2008-01-13 23:52:42 | Re: Index trouble with 8.3b4 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-01-14 00:30:44 | Re: Postgresql Materialized views |
| Previous Message | Tom Lane | 2008-01-14 00:01:26 | Re: Postgresql Materialized views |