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

• Re: SELECT * FROM <table> LIMIT 1; is really slow at 2004-05-29 01:59:53 from Alvaro Herrera

Responses

• Re: SELECT * FROM <table> LIMIT 1; is really slow at 2004-06-01 12:53:50 from Alvaro Herrera

pgsql-hackers by date

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