| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql's FETCH_COUNT (cursor) is not being respected for CTEs |
| Date: | 2023-01-04 16:36:51 |
| Message-ID: | 2097213.1672850211@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Jan 4, 2023 at 10:22 AM Daniel Verite <daniel(at)manitou-mail(dot)org> wrote:
>> A solution would be for psql to use PQsetSingleRowMode() to retrieve
>> results row-by-row, as opposed to using a cursor, and then allocate
>> memory for only FETCH_COUNT rows at a time.
> Is there any reason that someone hasn't, like, already done this?
As you well know, psql's FETCH_COUNT mechanism is far older than
single-row mode. I don't think anyone's tried to transpose it
onto that. I agree that it seems like a good idea to try.
There will be more per-row overhead, but the increase in flexibility
is likely to justify that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2023-01-04 16:43:46 | Re: Infinite Interval |
| Previous Message | Robert Haas | 2023-01-04 15:57:28 | Re: psql's FETCH_COUNT (cursor) is not being respected for CTEs |