Making ParameterStatus available for more parameter types?

From: Shay Rojansky <roji(at)roji(dot)org>
To: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Making ParameterStatus available for more parameter types?
Date: 2015-07-12 09:30:34
Message-ID: CADT4RqADmhP-CySD8pCfFp0UtF+NgJcPmgP+3ri5gMu_vd_iRA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi everyone.

The ParameterStatus message is currently sent for a hard-wired set of
parameters (
http://www.postgresql.org/docs/current/static/protocol-flow.html#PROTOCOL-ASYNC
).

Just wanted to let you know that making this more flexible would be a great
help in driver implementation. Npgsql maintains its own view of the current
statement_timeout parameter for various reasons; as long as the standard
ADO.NET API is used to change the timeout everything is OK, but if the user
ever manually sets statement_timeout things can become quite messy. Being
able to subscribe to more parameter changes would help in this case. In the
very short term simply adding statement_timeout to the hard-wired set would
help me as well.

Thanks,

Shay

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2015-07-12 09:35:01 Re: [PATCH] Generalized JSON output functions
Previous Message Yaroslav 2015-07-12 08:59:07 A little RLS oversight?