Skip site navigation (1) Skip section navigation (2)

Re: updated patch for selecting large results sets

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org, chrisnospam(at)1006(dot)org
Subject: Re: updated patch for selecting large results sets
Date: 2006-08-28 23:51:28
Message-ID: 200608282351.k7SNpS311444@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us
  EnterpriseDB    http://www.enterprisedb.com

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

In response to

pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2006-08-29 00:23:54
Subject: Re: Rtree circle ops
Previous:From: Chris MairDate: 2006-08-28 23:31:04
Subject: Re: updated patch for selecting large results sets in

pgsql-patches by date

Next:From: Bruno Wolff IIIDate: 2006-08-29 01:54:46
Subject: Re: [HACKERS] Performance testing of COPY (SELECT) TO
Previous:From: Chris MairDate: 2006-08-28 23:31:04
Subject: Re: updated patch for selecting large results sets in

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group