| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
| Cc: | Divakar Singh <dpsmails(at)yahoo(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Insert performance with composite index |
| Date: | 2010-11-02 09:45:39 |
| Message-ID: | 20101102094539.GA6686@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Nov 01, 2010 at 02:57:56PM +0100, Cédric Villemain wrote:
> > CONSTRAINT tableindex_pkey PRIMARY KEY (tableindex)
> > )
> > the index definition is
> > CREATE INDEX "PK_AT2"
> > ON ABC
> > USING btree
> > (event, tableindex)
> > TABLESPACE sample;
>
> Indexing twice the same column is useless. (perhaps move your PK to
> the tablespace 'sample' is good too ?)
why do you say that?
these are not the same indexes and they serve different purposes.
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: depesz(at)depesz(dot)com / aim:depeszhdl / skype:depesz_hdl / gg:6749007
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2010-11-02 11:04:42 | Re: Insert performance with composite index |
| Previous Message | Yaocl | 2010-11-02 02:50:22 | A query become very slow after upgrade from 8.1.10 to 8.4.5 |