| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-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. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2006-08-29 00:23:54 | Re: Rtree circle ops |
| Previous Message | Chris Mair | 2006-08-28 23:31:04 | Re: updated patch for selecting large results sets in |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2006-08-29 01:54:46 | Re: [HACKERS] Performance testing of COPY (SELECT) TO |
| Previous Message | Chris Mair | 2006-08-28 23:31:04 | Re: updated patch for selecting large results sets in |