Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan - Mailing list pgsql-hackers

From Don Baccus
Subject Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan
Date
Msg-id 3.0.1.32.20000821071438.014e07c0@mail.pacifier.com
Whole thread Raw
In response to Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan  (Hannu Krosing <hannu@tm.ee>)
List pgsql-hackers
At 01:34 PM 8/21/00 +0100, Tiago Antão wrote:
>Hi!
>
>On Mon, 21 Aug 2000, Hannu Krosing wrote:
>
>> And predictability is GOOD ;)
>> 
>> I would even suggest that PG would warn about or even refuse to run
>> queries 
>> that have both nextval and curval of the same sequence inside them 
>> (and pre-evaluate nextval) as only that case has _any_ predictability.
>
>
> Isn't the problem more general than just nextval?

Yes, it is.  



- Don Baccus, Portland OR <dhogaza@pacifier.com> Nature photos, on-line guides, Pacific Northwest Rare Bird Alert
Serviceand other goodies at http://donb.photo.net.
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: AW: pg_attribute growing and growing and growing
Next
From: Don Baccus
Date:
Subject: Re: Bug tracking (was Re: +/- Inf for float8's)