On Tue, Jul 15, 2008 at 12:19 AM, Edoardo Panfili <[EMAIL PROTECTED]> wrote:
> Scott Marlowe ha scritto:
>>
>> On Mon, Jul 14, 2008 at 1:54 PM, Chris Hoy <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Hi
>>>
>>> I have a number of tables in my database where the queries appear to
>>> ignoring the primary ke
On þri, 2008-07-15 at 08:19 +0200, Edoardo Panfili wrote:
> Scott Marlowe ha scritto:
> > On Mon, Jul 14, 2008 at 1:54 PM, Chris Hoy <[EMAIL PROTECTED]> wrote:
> >>
> >> select * from industries where industryid = 1;
> >> "Seq Scan on industries (cost=0.00..1.02 rows=1 width=116) (actual
> >> time
Scott Marlowe ha scritto:
On Mon, Jul 14, 2008 at 1:54 PM, Chris Hoy <[EMAIL PROTECTED]> wrote:
Hi
I have a number of tables in my database where the queries appear to
ignoring the primary key and doing a seq scan instead, however other tables
appear to be fine. I can see any difference between
On Mon, Jul 14, 2008 at 1:54 PM, Chris Hoy <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I have a number of tables in my database where the queries appear to
> ignoring the primary key and doing a seq scan instead, however other tables
> appear to be fine. I can see any difference between them.
>
> Is thei
Hi
I have a number of tables in my database where the queries appear to
ignoring the primary key and doing a seq scan instead, however other tables
appear to be fine. I can see any difference between them.
Is their any way of determination why the otimizer isn't picking up the
primary key?
Vers
