| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | libpq: Trace StartupMessage/SSLRequest/GSSENCRequest correctly |
| Date: | 2024-06-05 11:52:59 |
| Message-ID: | CAGECzQTTN5aGqtDaRifJXPyd_O5qHWQcOxsHJsDSVNqMugGNEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
While working on my patchset for protocol changes I realized that the
StartupMessage/SSLRequest/GSSENCRequest was not shown correctly in the
tracing output of libpq. With this change these messages are now shown
correctly in the tracing output.
To test you can add a PQreset(conn) call to the start of the
test_cancel function in
src/test/modules/libpq_pipeline/libpq_pipeline.c.
And then run:
ninja -C build all install-quiet &&
build/src/test/modules/libpq_pipeline/libpq_pipeline cancel
'port=5432' -t test.trace
And then look at the top of test.trace
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-libpq-Trace-StartupMessage-SSLRequest-GSSENCReque.patch | application/x-patch | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2024-06-05 12:28:05 | Re: Fix use of possible uninitialized variable retval (src/pl/plpgsql/src/pl_handler.c) |
| Previous Message | Ashutosh Bapat | 2024-06-05 11:39:58 | Re: Test to dump and restore objects left behind by regression |