Re: Slow UPADTE, compared to INSERT

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Ivar Zarans <iff(at)alcaron(dot)ee>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow UPADTE, compared to INSERT
Date: 2003-12-05 02:15:52
Message-ID: 3FCFEA58.7090505@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> Why first example, where recid is given as numeric constant, is using
> sequential scan, but second example, where recid is given as string
> constant works with index scan, as expected? Third example shows, that
> numeric constant must be typecasted in order to function properly.
>
> Is this normal behaviour of fields with bigint type?

Yes, it's a known performance problem in PostgreSQL 7.4 and below. I
believe it's been fixed in 7.5 CVS already.

Chris

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Eric Soroos 2003-12-05 04:52:22 Re: tuning questions
Previous Message Ivar Zarans 2003-12-05 02:07:28 Re: Slow UPADTE, compared to INSERT