Received: from rgate.ricochet.net (rgate.ricochet.net [204.179.143.6]) by
	hub.org (8.8.8/8.7.5) with ESMTP id VAA15004;
	Sun, 26 Apr 1998 21:07:17 -0400 (EDT)
Received: from [204.179.136.2] (mg136-002.ricochet.net [204.179.136.2])
	by rgate.ricochet.net (8.8.8/8.8.8) with ESMTP id TAA17578;
	Sun, 26 Apr 1998 19:53:57 -0500 (CDT)
X-Sender: kamesan@pop.ricochet.net
Message-Id: <l03110705b1698217f47d@[204.179.136.2]>
In-Reply-To: <199804262341.TAA07189@candle.pha.pa.us>
References: <1360.893632408@sss.pgh.pa.us> from "Tom Lane" at Apr 26, 98
	07:13:28 pm
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sun, 26 Apr 1998 17:55:54 -0700
To: Bruce Momjian <maillist@candle.pha.pa.us>, tgl@sss.pgh.pa.us (Tom Lane)
From: Michael Hirohama <kamesan@ricochet.net>
Subject: Re: retrieving varchar size
Cc: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org

The historical reason why the POSTGRES backend is required to send multiple
result sets is to support cursors on queries involving type inheritance and
anonymous target lists.

	begin
	declare c cursor for
		select e.oid, e.* from EMP* e
	fetch 10 in c
	...

To handle the command sequence above, frontend applications would need to
be provided with a new result descriptor when the "fetch 10 in c" crosses a
result set boundary.