| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Jelte Fennema <postgres(at)jeltef(dot)nl> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kirk Wolak <wolakk(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: proposal: psql: show current user in prompt |
| Date: | 2023-08-28 11:58:55 |
| Message-ID: | CAFj8pRBoq38P4b_nX0fEv17TrzfowYo6H9zga92_-9xsrxXmOg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
>>
>>
>> But afaict there's no problem with using pqParseInput3() and
>> PQexecFinish() even if the message isn't handled as part of the
>> transaction. Some other messages that pqParseInput3 handles which are
>> not part of the transaction are 'N' (Notice) and 'K' (secret key).
>>
>
> I have to recheck it
>
here is new version based on usage of PQexecFinish
Regards
Pavel
>
> Regards
>
> Pavel
>
>
| Attachment | Content-Type | Size |
|---|---|---|
| 0002-Implementation-of-N-prompt-placeholder.patch | text/x-patch | 6.0 KB |
| 0001-Protocol-ReportGUC-message.patch | text/x-patch | 10.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2023-08-28 12:00:26 | Re: Wrong usage of pqMsg_Close message code? |
| Previous Message | Hayato Kuroda (Fujitsu) | 2023-08-28 11:48:14 | RE: persist logical slots to disk during shutdown checkpoint |