From: Hannu Krosing <hannu@2ndquadrant.com>
To: Beaver, John E <John_Beaver@hms.harvard.edu>
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: Sat, 03 Apr 2010 01:18:08 +0300
Message-ID: <1270246688.6482.263.camel@hvost> (raw)
In-Reply-To: <62307826D0C1F74BAFE47B6747FA8C2C5407AED155@ITCCRMAIL02.MED.HARVARD.EDU>
References: <62307826D0C1F74BAFE47B6747FA8C2C5407AED155@ITCCRMAIL02.MED.HARVARD.EDU>
On Fri, 2010-04-02 at 16:28 -0400, Beaver, John E wrote:
...
> 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.
COPY can copy out results of a SELECT query as well.
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
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: hannu@2ndquadrant.com, John_Beaver@hms.harvard.edu
Subject: Re: Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
In-Reply-To: <1270246688.6482.263.camel@hvost>
* 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