Re: psql FETCH_COUNT feature does not work with combined queries

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: psql FETCH_COUNT feature does not work with combined queries
Date: 2020-03-27 22:53:03
Message-ID: alpine.DEB.2.21.2003272340190.16227@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

>> Assuming there's no one willing to fix the behavior (and that seems
>> unlikely given we're in the middle of a 2020-01 commitfest) it makes
>> sense to at least document the behavior.
>> That being said, I think the proposed patch may be a tad too brief. I
>> don't think we need to describe the exact behavior, of course, but maybe
>> it'd be good to mention that the behavior depends on the type of the
>> last command etc. Also, I don't think "combined query" is a term used
>> anywhere in the code/docs - I think the proper term is "multi-query
>> string".
> Any thoughts on Tomas' comments?

Sorry, I did not notice them.

I tried "multi-command", matching some wording use elsewhere in the file.
I'm at lost about how to describe the insane behavior the feature has when
they are used, which is really just an unfixed bug, so I expanded a minima
in the attached v2.


Attachment Content-Type Size
psql-fetch-count-doc-2.patch text/x-diff 651 bytes

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2020-03-27 22:59:07 Re: Berserk Autovacuum (let's save next Mandrill)
Previous Message Nikita Glukhov 2020-03-27 22:43:35 Re: fix for BUG #3720: wrong results at using ltree