From: John Beaver <john_beaver@hms.harvard.edu>
To: Hannu Krosing <hannu@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
Date: Fri, 2 Apr 2010 18:18:46 -0400
Message-ID: <4BB66D46.3050703@hms.harvard.edu> (raw)
In-Reply-To: <1270246688.6482.263.camel@hvost>
References: <62307826D0C1F74BAFE47B6747FA8C2C5407AED155@ITCCRMAIL02.MED.HARVARD.EDU>
<1270246688.6482.263.camel@hvost>
<!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">
Ah, you're right. Thanks Hannu, that's a good solution.<br>
<br>
Hannu Krosing wrote:
<blockquote cite="mid:1270246688.6482.263.camel@hvost" type="cite">
<pre wrap="">On Fri, 2010-04-02 at 16:28 -0400, Beaver, John E wrote:
...
</pre>
<blockquote type="cite">
<pre wrap="">I know that the query used here could have been a COPY statement, which I assume would
be better-behaved, but I'm more concerned about the case in which the query is more complex.
</pre>
</blockquote>
<pre wrap=""><!---->
COPY can copy out results of a SELECT query as well.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
John E. Beaver
Bioinformatics Developer
Harvard Medical School</pre>
</body>
</html>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: john_beaver@hms.harvard.edu, hannu@2ndquadrant.com
Subject: Re: Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
In-Reply-To: <4BB66D46.3050703@hms.harvard.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox