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 200608282351.k7SNpS311444@momjian.us
Whole thread Raw
In response to Re: [PATCHES] updated patch for selecting large results sets  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > 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.
>
> I'm willing to accept this if we can make sure we aren't adding any
> overhead --- see my proposal elsewhere in the thread for fixing that.

Right, if \g has overhead, I don't want people to start using ; because
it is faster.  That is the kind of behavior that makes us look sloppy.

--
  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: Chris Mair
Date:
Subject: Re: [PATCHES] updated patch for selecting large results sets in
Next
From: Tatsuo Ishii
Date:
Subject: Re: Rtree circle ops