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

From: "Pierre C" <lists(at)peufeu(dot)com>
To: "Beaver, John E" <John_Beaver(at)hms(dot)harvard(dot)edu>, "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 20:43:16
Message-ID: op.vajyiejneorkce@immo.peufeu.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> 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.

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.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next 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?
Previous Message Beaver, John E 2010-04-02 20:28:30 Does the psql executable support a "fetch many" approach when dumping large queries to stdout?