pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: M. Scott Smith <mssmit1@afterlife.ncsc.mil>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Problem with limit / union / etc.
Date: Tue, 28 Dec 1999 15:13:25 -0500
Message-ID: <28951.946412005@sss.pgh.pa.us> (raw)
In-Reply-To: <199912281615.LAA13003@afterlife.ncsc.mil>
References: <199912281615.LAA13003@afterlife.ncsc.mil>

"M. Scott Smith" <mssmit1@afterlife.ncsc.mil> writes:
>    What I want to do is pull out upcoming events, limiting the number
> returned.  The following query is my attempt to do that.  The
> first select selects all events that have a URL associated with
> them; the second query selects all events that DON'T have a URL
> associated with them; the results are combined together.  My
> hope is that the order by/limit clause will limit the results returned
> after they are combined, but it seems to be ignoring this.

Yeah, there's a bug in 6.5.* that causes it to ignore LIMIT on a UNION.
I fixed it a couple months ago, but there's been no new release since
then.  Here's the patch, if you want to patch your copy:

inline patch 1: src/backend/rewrite/rewriteHandler.c (+6/-0 lines) download inline-1.patch*** src/backend/rewrite/rewriteHandler.c~ Sun Jul 11 13:54:30 1999 --- src/backend/rewrite/rewriteHandler.c Tue Oct 19 00:38:05 1999 *************** *** 2859,2864 **** --- 2859,2866 ---- bool isBinary, isPortal, isTemp; + Node *limitOffset, + *limitCount; CmdType commandType = CMD_SELECT; List *rtable_insert = NIL; *************** *** 2909,2914 **** --- 2911,2918 ---- isBinary = parsetree->isBinary; isPortal = parsetree->isPortal; isTemp = parsetree->isTemp; + limitOffset = parsetree->limitOffset; + limitCount = parsetree->limitCount; /* * The operator tree attached to parsetree->intersectClause is still *************** *** 3094,3099 **** --- 3098,3105 ---- result->isPortal = isPortal; result->isBinary = isBinary; result->isTemp = isTemp; + result->limitOffset = limitOffset; + result->limitCount = limitCount; /* * The relation to insert into is attached to the range table of the
regards, tom lane

view thread (3+ messages)

Message-ID: <28951.946412005@sss.pgh.pa.us>
Permalink:  ../28951.946412005@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28951.946412005@sss.pgh.pa.us

 ·  · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mssmit1@afterlife.ncsc.mil
  Subject: Re: [SQL] Problem with limit / union / etc.
  In-Reply-To: <28951.946412005@sss.pgh.pa.us>
  References: <199912281615.LAA13003@afterlife.ncsc.mil> <28951.946412005@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox