Re: fetching unique pins in a high-transaction

From: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
To: Bobus <roblocke(at)gmail(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: fetching unique pins in a high-transaction
Date: 2006-11-04 18:12:12
Message-ID: C172260C.5A1A6%scott_ribe@killerbytes.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> That second query may not be the best, as it will probably seqscan and
> grab all the pins before only returning the first one ...

A partial index where USED_BY is null would eliminate the need for the
seqscan on the table...

--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 722-0567 voice

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Raymond O'Donnell 2006-11-04 18:38:20 Re: bytea / large object and image
Previous Message Stephan Szabo 2006-11-04 17:28:08 Re: Simple stored procedure examples?