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

From: John Beaver <john_beaver(at)hms(dot)harvard(dot)edu>
To: Pierre C <lists(at)peufeu(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: *** PROBABLY SPAM *** Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
Date: 2010-04-02 22:19:38
Message-ID: 4BB66D7A.1090605@hms.harvard.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
That makes sense. I'll just use a COPY statement instead like Hannu
suggests.<br>
<br>
Pierre C wrote:
<blockquote cite="mid:op(dot)vajyiejneorkce(at)immo(dot)peufeu(dot)com" type="cite">
<blockquote type="cite">
<pre wrap="">Does the psql executable have any 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>
</body>
</html>

Attachment Content-Type Size
unknown_filename text/html 1.0 KB

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message David Crooke 2010-04-03 05:05:14 David Crooke wants to stay in touch on LinkedIn
Previous Message John Beaver 2010-04-02 22:18:46 Re: Does the psql executable support a "fetch many" approach when dumping large queries to stdout?