From: Ivar Zarans <iff@alcaron.ee>
To: pgsql-performance@postgresql.org
Subject: Re: Slow UPADTE, compared to INSERT
Date: Fri, 5 Dec 2003 15:13:25 +0200
Message-ID: <20031205131325.GB27524@alcaron.ee> (raw)
In-Reply-To: <3FD07EEA.8030007@persistent.co.in>
References: <20031204185751.GA15893@alcaron.ee>
<20031205014514.GA21079@alcaron.ee>
<20031205020728.GA21440@alcaron.ee>
<200312051008.20317.dev@archonet.com>
<20031205123843.GA27170@alcaron.ee>
<3FD07EEA.8030007@persistent.co.in>
On Fri, Dec 05, 2003 at 06:19:46PM +0530, Shridhar Daithankar wrote:
> >is correct SQL, but not correct, considering PostgreSQL bugs.
>
> Personally I don't consider a bug but anyways.. You are the one facing
> problem so I understand..
Well, if this is not bug, then what is consideration behind this
behaviour? BTW, according to Cristopher it is fixed in 7.5 CVS.
Why fix it if this is not a bug? :))
One more question - is this "feature" related only to "bigint" fields,
or are other datatypes affected as well?
> Will following help?
>
> qry = "UPDATE table1 SET status = %s WHERE recid = '%s'"
> cursor.execute(qry, status, recid)
Yes, this helps. But then it sort of obsoletes PyPgSQL-s own quoting
logic. I would prefer to take care of this all by myself or trust some
underlying code to do this for me. And PyPgSQL is quite nice - it
checks datatype and acts accordingly.
--
Ivar
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: iff@alcaron.ee
Subject: Re: Slow UPADTE, compared to INSERT
In-Reply-To: <20031205131325.GB27524@alcaron.ee>
* 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