From: Vivek Khera <khera@kcilink.com>
To: pgsql-general@postgresql.org
Subject: Re: [ADMIN] Q: Structured index - which one runs faster?
Date: Fri, 23 May 2003 14:04:28 -0400
Message-ID: <16078.25260.512996.337914@yertle.int.kciLink.com> (raw)
In-Reply-To: <17188.1053711517@sss.pgh.pa.us>
References: <5.1.1.6.2.20030522223909.05929600@mail.vogelsinger.at>
<11951.1053643980@sss.pgh.pa.us>
<x7ptm94s4z.fsf@yertle.int.kciLink.com>
<17188.1053711517@sss.pgh.pa.us>
>>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.us> writes:
>> In particular, is user_list_owner_id redundant to
>> user_list_oid_created?
TL> Any of the three indexes can be used for a search on owner_id alone, so
TL> yeah, user_list_owner_id is redundant. It would be marginally faster to
TL> use user_list_owner_id for such a search, just because it's physically
TL> smaller than the other two indexes, but against that you have to balance
TL> the extra update cost of maintaining the additional index.
This is great info. That extra index is gonna be nuked in about 37.23
seconds... It takes up a lot of space and is wasting time with
updates and inserts, which happen a *lot* on that table (nearly 10
million rows).
Thanks!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: khera@kcilink.com, pgsql-general@postgresql.org
Subject: Re: [ADMIN] Q: Structured index - which one runs faster?
In-Reply-To: <16078.25260.512996.337914@yertle.int.kciLink.com>
References: <5.1.1.6.2.20030522223909.05929600@mail.vogelsinger.at> <11951.1053643980@sss.pgh.pa.us> <x7ptm94s4z.fsf@yertle.int.kciLink.com> <17188.1053711517@sss.pgh.pa.us> <16078.25260.512996.337914@yertle.int.kciLink.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox