From: | Jeremy Harris <jgh(at)wizmail(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: why postgresql over other RDBMS |
Date: | 2007-06-02 17:08:41 |
Message-ID: | 4661A419.5050408@wizmail.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 06/01/07 11:22, Bruce Momjian wrote:
> > PFC wrote:
>> >> On Thu, 31 May 2007 22:20:09 +0200, Vivek Khera <vivek(at)khera(dot)org> wrote:
>> >>
>>> >>> On May 25, 2007, at 5:28 PM, Tom Lane wrote:
>>> >>>
>>>> >>>> That's true at the level of DDL operations, but AFAIK we could
>>>> >>>> parallelize table-loading and index-creation steps pretty effectively
>>>> >>>> --- and that's where all the time goes.
>>> >>> I would be happy with parallel builds of the indexes of a given table.
>>> >>> That way you have just one scan of the whole table to build all its
>>> >>> indexes.
>> >> Will the synchronized seq scan patch be able to do this by issuing all
>> >> the CREATE INDEX commands at the same time from several different database
>> >> connections ?
> >
> > No, but it could someday.
Would it be possible to track stats sufficient for a cost/benefit based
automatic recreate of all indices on a table whenever a full-table-scan
occurred, whether due to a commanded index rebuild or not?
Cheers,
Jeremy Harris
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Glaesemann | 2007-06-02 17:51:25 | Re: Transactional DDL |
Previous Message | Harpreet Dhaliwal | 2007-06-02 16:46:54 | Re: Transactional DDL |