Re: *** PROBABLY SPAM *** Does the psql executable support a "fetch many" approach when dumping large queries to stdout? - Mailing list pgsql-performance

From John Beaver
Subject Re: *** PROBABLY SPAM *** Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
Date
Msg-id 4BB66D7A.1090605@hms.harvard.edu
Whole thread Raw
In response to Re: *** PROBABLY SPAM *** Does the psql executable support a "fetch many" approach when dumping large queries to stdout?  ("Pierre C" <lists@peufeu.com>)
List pgsql-performance
That makes sense. I'll just use a COPY statement instead like Hannu suggests.<br /><br /> Pierre C wrote: <blockquote
cite="mid:op.vajyiejneorkce@immo.peufeu.com"type="cite"><blockquote type="cite"><pre wrap="">Does the psql executable
haveany ability to do a "fetch many", using a  
 
server-side named cursor, when returning results? It seems like it tries  
to retrieve the query entirely to local memory before printing to  
standard out.   </pre></blockquote><pre wrap="">
I think it grabs the whole result set to calculate the display column  
widths. I think there is an option to tweak this but don't remember which,  
have a look at the psql commands (\?), formatting section. </pre></blockquote><br /><pre class="moz-signature"
cols="72">--
 
John E. Beaver
Bioinformatics Developer
Harvard Medical School</pre>

pgsql-performance by date:

Previous
From: John Beaver
Date:
Subject: Re: Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
Next
From: David Crooke
Date:
Subject: David Crooke wants to stay in touch on LinkedIn