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

Re: BUG #2475: Row limit problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Sebastiaan van Erk" <sebster-postgresql(at)sebster(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2475: Row limit problem
Date: 2006-06-10 23:30:19
Message-ID: 3375.1149982219@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Sebastiaan van Erk" <sebster-postgresql(at)sebster(dot)com> writes:
> This shows the ENORMOUS different time it takes for the  two queries even
> though they both have the limit set.

So?  They're not the same query.  (In particular, the row limit in the
protocol only says how many rows to deliver in the first batch.  The
presumption is that you'll eventually grab the rest, and so the query
is planned on that basis.)

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-06-10 23:32:04
Subject: Re: BUG #2474: cp: cannot access ~/archivedir/00000001.history
Previous:From: Tom LaneDate: 2006-06-10 16:38:20
Subject: Re: Fwd: Bug#372115: Last security update of postgresql-contrib breaks database replication with DBMirror.pl

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