Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan

From: Don Baccus <dhogaza(at)pacifier(dot)com>
To: Tiago Antão <tra(at)fct(dot)unl(dot)pt>, Hannu Krosing <hannu(at)tm(dot)ee>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan
Date: 2000-08-21 14:14:38
Message-ID: 3.0.1.32.20000821071438.014e07c0@mail.pacifier.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-08-21 14:23:37 Re: AW: pg_attribute growing and growing and growing
Previous Message Don Baccus 2000-08-21 13:59:06 Re: Bug tracking (was Re: +/- Inf for float8's)