From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Subject: | Re: Batch update of indexes on data loading |
Date: | 2008-02-22 02:26:24 |
Message-ID: | 200802211826.24437.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Itagaki-san,
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> > > The basic concept is spooling new coming data, and merge the spool and
> > > the existing indexes into a new index at the end of data loading. It is
> > > 5-10 times faster than index insertion per-row, that is the way in 8.3.
Thanks so much for doing this. For one thing, it will vastly improve
PostgreSQL's ability to run industry-standard benchmarks. As well as making
dump/reload much less painful.
> I heard it is used in Falcon storage engine in MySQL, so it seems to be
> not so unrealistic approach.
I don't think we want to copy any spec from Falcon ... it's a year (or more)
behind schedule.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-02-22 02:33:03 | Re: Including PL/PgSQL by default |
Previous Message | Josh Berkus | 2008-02-22 02:24:35 | Re: Including PL/PgSQL by default |