Re: Improve OAuth discovery logging - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: Improve OAuth discovery logging
Date
Msg-id CAN4CZFOmym1BaV_U2V56aOyRp2JMrw5nfn6kwcAEcu_RWK-F3Q@mail.gmail.com
Whole thread
In response to Re: Improve OAuth discovery logging  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: Improve OAuth discovery logging
List pgsql-hackers
> I'm experimenting with an ereport(FATAL_CLIENT_ONLY) option, in the
> same vein as WARNING_CLIENT_ONLY, to try to cover this.

I attached v7 that uses that and removes the abandoned handling as it
is no longer needed with it.

> P.S. I would eventually like to record our undocumented SASL profile
> in a test suite (he said, staring at pg-pytest)...

That would be definitely useful, with the todo comment and this not
being documented I thought that this is a proper way to handle the
issue. Even a proper documentation about it would be a good starting
point.

Attachment

pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: gen_guc_tables improvements
Next
From: Michael Paquier
Date:
Subject: Re: Flush some statistics within running transactions