Re: [HACKERS] selecting large result sets in psql using - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: [HACKERS] selecting large result sets in psql using
Date
Msg-id 200608171630.k7HGUY609152@momjian.us
Whole thread Raw
In response to Re: selecting large result sets in psql using cursors  (Chris Mair <chrisnospam@1006.org>)
Responses Re: [HACKERS] selecting large result sets in psql using  (Chris Mair <chrisnospam@1006.org>)
Re: [HACKERS] selecting large result sets in psql using cursors  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Chris Mair wrote:
> > At some point we ought to extend libpq enough to expose the V3-protocol
> > feature that allows partial fetches from portals; that would be a
> > cleaner way to implement this feature.  However since nobody has yet
> > proposed a good API for this in libpq, I don't object to implementing
> > \u with DECLARE CURSOR for now.
> >
> > BTW, \u seems not to have any mnemonic value whatsoever ... isn't there
> > some other name we could use?
>
> True :)
> Since buffer commands all have a single char I wanted a single char one
> too. The "c" for "cursor" was taken already, so i choose the "u" (second
> char in "cursor"). If somebody has a better suggestion, let us know ;)

I think a new backslash variable isn't the way to go.  I would use a
\pset variable to control what is happening.

--
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-patches by date:

Previous
From: "Matthew T. O'Connor"
Date:
Subject: Re: [HACKERS] Autovacuum maintenance window (was Re: Adjust autovacuum
Next
From: Chris Mair
Date:
Subject: Re: [HACKERS] selecting large result sets in psql using