Re: Insert performance with composite index - Mailing list pgsql-performance

From Cédric Villemain
Subject Re: Insert performance with composite index
Date
Msg-id AANLkTi=FpwtFLp07ZP36DzLFhpE0xdmQW6O=_rEyM5ov@mail.gmail.com
Whole thread Raw
In response to Re: Insert performance with composite index  (hubert depesz lubaczewski <depesz@depesz.com>)
Responses Re: Insert performance with composite index  (hubert depesz lubaczewski <depesz@depesz.com>)
Re: Insert performance with composite index  (Divakar Singh <dpsmails@yahoo.com>)
List pgsql-performance
2010/11/2 hubert depesz lubaczewski <depesz@depesz.com>:
> 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.

Given that tableindex is the PK column, I really like to now the usage
pattern for having it indexed twice.

>
> Best regards,
>
> depesz
>
> --
> Linkedin: http://www.linkedin.com/in/depesz  /  blog: http://www.depesz.com/
> jid/gtalk: depesz@depesz.com / aim:depeszhdl / skype:depesz_hdl / gg:6749007
>



--
Cédric Villemain               2ndQuadrant
http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support

pgsql-performance by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: Insert performance with composite index
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: Insert performance with composite index