From: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
---|---|
To: | depesz(at)depesz(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 11:04:42 |
Message-ID: | AANLkTi=FpwtFLp07ZP36DzLFhpE0xdmQW6O=_rEyM5ov@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
2010/11/2 hubert depesz lubaczewski <depesz(at)depesz(dot)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(at)depesz(dot)com / aim:depeszhdl / skype:depesz_hdl / gg:6749007
>
--
Cédric Villemain 2ndQuadrant
http://2ndQuadrant.fr/ PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2010-11-02 11:53:27 | Re: Insert performance with composite index |
Previous Message | hubert depesz lubaczewski | 2010-11-02 09:45:39 | Re: Insert performance with composite index |