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

Re: [PATCHES] updated patch for selecting large results sets in psql using cursors

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

In response to

Responses

pgsql-hackers by date

Next:From: Zoltan BoszormenyiDate: 2006-08-28 17:46:26
Subject: Re: [HACKERS] Performance testing of COPY (SELECT) TO
Previous:From: Alvaro HerreraDate: 2006-08-28 17:40:31
Subject: Re: [HACKERS] Performance testing of COPY (SELECT) TO

pgsql-patches by date

Next:From: Zoltan BoszormenyiDate: 2006-08-28 17:46:26
Subject: Re: [HACKERS] Performance testing of COPY (SELECT) TO
Previous:From: Alvaro HerreraDate: 2006-08-28 17:40:31
Subject: Re: [HACKERS] Performance testing of COPY (SELECT) TO

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