Postgres Pro
Downloads
Home   >   mailing lists

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

From Pierre C
Subject Re: *** PROBABLY SPAM *** Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
Date
Msg-id op.vajyiejneorkce@immo.peufeu.com
Whole thread Raw
In response to Does the psql executable support a "fetch many" approach when dumping large queries to stdout?  ("Beaver, John E" <John_Beaver@hms.harvard.edu>)
Responses Re: *** PROBABLY SPAM *** Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
Re: *** PROBABLY SPAM *** Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
List pgsql-performance
Tree view 
> 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.

pgsql-performance by date:

Previous
From: "Beaver, John E"
Date:
Subject: Does the psql executable support a "fetch many" approach when dumping large queries to stdout?
Next
From: John Beaver
Date:
Subject: Re: Does the psql executable support a "fetch many" approach when dumping large queries to stdout?