| From: | John Beaver <john_beaver(at)hms(dot)harvard(dot)edu> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Does the psql executable support a "fetch many" approach when dumping large queries to stdout? |
| Date: | 2010-04-02 22:18:46 |
| Message-ID: | 4BB66D46.3050703@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">
Ah, you're right. Thanks Hannu, that's a good solution.<br>
<br>
Hannu Krosing wrote:
<blockquote cite="mid:1270246688(dot)6482(dot)263(dot)camel(at)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>
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/html | 919 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Beaver | 2010-04-02 22:19:38 | Re: *** PROBABLY SPAM *** Does the psql executable support a "fetch many" approach when dumping large queries to stdout? |
| Previous Message | Hannu Krosing | 2010-04-02 22:18:08 | Re: Does the psql executable support a "fetch many" approach when dumping large queries to stdout? |