From: Richard Huxton <dev@archonet.com>
To: Ivar Zarans <iff@alcaron.ee>
To: pgsql-performance@postgresql.org
Subject: Re: Slow UPADTE, compared to INSERT
Date: Fri, 5 Dec 2003 10:08:20 +0000
Message-ID: <200312051008.20317.dev@archonet.com> (raw)
In-Reply-To: <20031205020728.GA21440@alcaron.ee>
References: <20031204185751.GA15893@alcaron.ee>
<20031205014514.GA21079@alcaron.ee>
<20031205020728.GA21440@alcaron.ee>
On Friday 05 December 2003 02:07, Ivar Zarans wrote:
> I have played around with explain and explain analyze and noticed one
> interesting oddity:
[snip]
> 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?
As Christopher says, normal (albeit irritating). Not sure it applies here -
all the examples you've shown me are using the index.
Well - I must admit I'm stumped. Unless you have a *lot* of indexes and
foreign keys to check, I can't see why it would take so long to update a
single row. Can you post the schema for the table?
--
Richard Huxton
Archonet Ltd
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dev@archonet.com, iff@alcaron.ee
Subject: Re: Slow UPADTE, compared to INSERT
In-Reply-To: <200312051008.20317.dev@archonet.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