Re: Identifying function-lookup failures due to argument name mismatches

2025-08-22 Thread Dominique Devienne
On Fri, Aug 22, 2025 at 12:58 AM Tom Lane wrote: > I wrote: > > Dunno, I think the new messages already cover all the interesting > > cases of argument name mismatch. I'm hesitant to touch the > > longstanding hint, and if I did I'd probably change it more than that, > > to something like > > > E

Re: Identifying function-lookup failures due to argument name mismatches

2025-08-18 Thread Dominique Devienne
On Thu, Aug 14, 2025 at 9:18 PM Tom Lane wrote: > I wrote: > > Another thing not to like is that it seems like this is doing violence > > to several APIs in exchange for not very much improvement in the error > > messages. I feel like maybe we ought to be trying for more > > specificity about add

Re: Improve the granularity of PQsocketPoll's timeout parameter?

2024-06-14 Thread Dominique Devienne
On Thu, Jun 13, 2024 at 9:18 PM Tom Lane wrote: > Ranier Vilela writes: > > +1 for push. > > Done. [...] Thanks a lot Tom (and reviewers)! --DD

Re: Improve the granularity of PQsocketPoll's timeout parameter?

2024-06-10 Thread Dominique Devienne
On Mon, Jun 10, 2024 at 11:39 PM Tom Lane wrote: > The next question is how to spell "int64" in libpq-fe.h. Hi. Out-of-curiosity, I grep'd for it in my 16.1 libpq: [ddevienne@marsu include]$ grep 'long long' *.h ecpg_config.h:/* Define to 1 if the system has the type `long long int'. */ ecpg_con