Re: [PATCHES] updated patch for selecting large results sets - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [PATCHES] updated patch for selecting large results sets
Date
Msg-id 200608282308.k7SN87317504@momjian.us
Whole thread Raw
In response to Re: [PATCHES] updated patch for selecting large results sets in psql using cursors  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] updated patch for selecting large results sets  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCHES] updated patch for selecting large results sets in  (Chris Mair <chrisnospam@1006.org>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Peter Eisentraut wrote:
> >> Tom Lane wrote:
> >>> Wait a minute.  What I thought we had agreed to was a patch to make
> >>> commands sent with \g use a cursor.
>
> > I am confused.  I assume \g and ; should be affected, like Peter says.
> > Tom, what *every* command are you talking about?  You mean \d?
>
> Like I said, I thought we were intending to modify \g's behavior only;
> that was certainly the implication of the discussion of "\gc".

OK, got it.  I just don't see the value to doing \g and not ;. I think
the \gc case was a hack when he didn't have \set.  Now that we have
\set, we should be consistent.

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

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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] updated patch for selecting large results sets in psql using cursors
Next
From: Tom Lane
Date:
Subject: Re: autovacuum causing numerous regression-test failures