Re: protocol support for labels

From: Jeremy Schneider <schneider(at)ardentperf(dot)com>
To: Nico Williams <nico(at)cryptonector(dot)com>
Cc: Frits Hoogland <frits(dot)hoogland(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Dave Cramer <davecramer(at)postgres(dot)rocks>, Sami Imseih <samimseih(at)gmail(dot)com>
Subject: Re: protocol support for labels
Date: 2025-03-13 06:39:57
Message-ID: 20250312233957.5f76c7a5@ardentperf.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 11 Mar 2025 14:03:12 -0500
Nico Williams <nico(at)cryptonector(dot)com> wrote:
> How about using a `set_config()` to deonte the "application_name" (and
> any other details) for the _next_ query, then have those details
> appear in the pg_stat_statements rows and logs?
>
> Clients would send a `SELECT set_config(...)` and also the next query
> one after the other without waiting for the response to the first.
> The server could similarly batch the two responses.

Isn't multiple queries in one packet only possible with the simple
protocol, but not possible with the extended protocol? So this would be
entirely incompatible with prepared/parameterized statements?

-Jeremy

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2025-03-13 06:42:57 Re: Vacuum statistics
Previous Message Dilip Kumar 2025-03-13 06:13:16 Re: Add an option to skip loading missing publication to avoid logical replication failure