Re: Index trouble with 8.3b4

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 01:43:19
Message-ID: 16961.1200274999@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

I wrote:
> I think it's okay for CREATE INDEX CONCURRENTLY to use bulk-read access
> strategy (that is, seqscan using a limited number of buffers), but it
> has to be able to force the scan to start at page zero.

I've committed a patch to do that. Please test CVS HEAD and see if you
still see problems.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-01-14 02:00:09 Re: What pg_restore does to a non-empty target database
Previous Message Trevor Talbot 2008-01-14 00:32:59 Re: How to safely compare transaction id?

Browse pgsql-hackers by date

  From Date Subject
Next Message Sean Utt 2008-01-14 01:44:25 Re: Postgresql Materialized views
Previous Message Andrew Dunstan 2008-01-14 01:30:59 Re: Postgresql Materialized views