Re: get/setReadOnly broken if default_transaction_read_only on

On Fri, Jun 8, 2012 at 6:47 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> There already is a mechanism to notify clients of changes in selected
> GUC settings, but currently the set of parameters so reported is
> hard-wired.  Possibly pgsql-hackers would consider a proposal to let
> the GUC_REPORT flag get set on client-selected parameters.

Somewhat off-topic, but along the same lines, it would also be worth
considering some mechanism to give the driver visibility into catalog
changes w.r.t. UDTs. I.e., right now, the only way for the driver to
sanely support custom types is to query the catalog for the oid of a
specific type name. However, if that type is subsequently dropped and
re-created and gets a different oid, the driver has no idea.
Unfortunately, I don't think there's a great way to support that
without protocol changes (whereas for the reporting flag, that's not
an issue).