Re: updated patch for selecting large results sets

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-patches(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, chrisnospam(at)1006(dot)org
Subject: Re: updated patch for selecting large results sets
Date: 2006-08-28 22:54:13
Message-ID: 200608282254.k7SMsDB16553@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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. This patch changes SendQuery
> > so that *every* command executed via psql is treated this way.
>
> That's what I remembered. I don't think we want to introduce a
> difference between ; and \g.

I am confused. I assume \g and ; should be affected, like Peter says.
Tom, what *every* command are you talking about? You mean \d?

--
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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-08-28 23:06:38 Re: updated patch for selecting large results sets in psql using cursors
Previous Message Bruce Momjian 2006-08-28 22:47:31 Re: [HACKERS] Performance testing of COPY (SELECT)

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-08-28 23:06:38 Re: updated patch for selecting large results sets in psql using cursors
Previous Message Bruce Momjian 2006-08-28 22:47:31 Re: [HACKERS] Performance testing of COPY (SELECT)