Skip site navigation (1) Skip section navigation (2)

Re: SELECT * FROM <table> LIMIT 1; is really slow

From: Manfred Koizar <mkoi-pg(at)aon(dot)at>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,David Blasby <dblasby(at)refractions(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SELECT * FROM <table> LIMIT 1; is really slow
Date: 2004-06-01 12:37:37
Message-ID: 6gtob0hvos04cm7ug7du53eroiqle1dr8t@email.aon.at (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, 28 May 2004 21:59:53 -0400, Alvaro Herrera
<alvherre(at)dcc(dot)uchile(dot)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.

Servus
 Manfred

In response to

Responses

pgsql-hackers by date

Next:From: Manfred KoizarDate: 2004-06-01 12:39:13
Subject: Re: SELECT * FROM <table> LIMIT 1; is really slow
Previous:From: Shridhar DaithankarDate: 2004-06-01 12:31:56
Subject: Re: Converting postgresql.conf parameters to kilobytes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group