| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, chrisnospam(at)1006(dot)org |
| Subject: | Re: [PATCHES] updated patch for selecting large results sets in psql using cursors |
| Date: | 2006-08-28 17:45:13 |
| Message-ID: | 13798.1156787113@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> 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.
Have we measured the performance impact, then? The last time I profiled
psql, GetVariable was already a hotspot, and this introduces another
call of it into the basic query loop whether you use the feature or not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltan Boszormenyi | 2006-08-28 17:46:26 | Re: [HACKERS] Performance testing of COPY (SELECT) TO |
| Previous Message | Alvaro Herrera | 2006-08-28 17:40:31 | Re: [HACKERS] Performance testing of COPY (SELECT) TO |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltan Boszormenyi | 2006-08-28 17:46:26 | Re: [HACKERS] Performance testing of COPY (SELECT) TO |
| Previous Message | Alvaro Herrera | 2006-08-28 17:40:31 | Re: [HACKERS] Performance testing of COPY (SELECT) TO |