Postgres Pro
Downloads
Home   >   mailing lists

Re: SELECT * FROM LIMIT 1; is really slow - Mailing list pgsql-hackers
From Manfred Koizar
Subject Re: SELECT * FROM LIMIT 1; is really slow
Date
Msg-id 6gtob0hvos04cm7ug7du53eroiqle1dr8t@email.aon.at
Whole thread Raw
In response to Re: SELECT * FROM LIMIT 1; is really slow  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Responses Re: SELECT * FROM LIMIT 1; is really slow
List pgsql-hackers
Tree view 
On Fri, 28 May 2004 21:59:53 -0400, Alvaro Herrera
<alvherre@dcc.uchile.cl> wrote:
>So the assumption was that when we see that this has
>happenned, the Cmin is no longer important (== every future command can
>already see the tuple)

If it was that simple, we wouldn't have had to invent the CMIN_IS_CMAX
flag.  This has been discussed two years ago.  Did you follow the link I
posted last week?  "Every future command" is not enough.  You have to
consider the current command and even commands started before this.

ServusManfred

pgsql-hackers by date:

Previous
From: Shridhar Daithankar
Date:
Subject: Re: Converting postgresql.conf parameters to kilobytes
Next
From: Manfred Koizar
Date:
Subject: Re: SELECT * FROM LIMIT 1; is really slow