On 4/23/19 11:52 AM, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/sql-set-role.html
> Description:
>
> In the course of trying to sanitise our roles and permissions I found the
> notes in the SET ROL
On 2019-04-24 13:22, Joe Conway wrote:
>> "Using a passphrase also disables the ability to change the server's
>>SSL configuration without a server restart."
>>
>> But as of pg11 we have ssl_passphrase_command_supports_reload, which as
>> I understand it should allow this if the passphrase co
I've added 5 more statements to the attached SQL to demonstrate the problem
in the last two SELECTs. Ran it against PG 11.2 provided by Docker Hub this
time and the problem is still visible.
On Thu, 11 Apr 2019 at 21:39, Bruce Momjian wrote:
> On Thu, Apr 4, 2019 at 02:54:29PM +, PG Doc com
(moved from Hackers to docs)
On 1/5/19 4:26 PM, Joe Conway wrote:
> On https://www.postgresql.org/docs/11/ssl-tcp.html it says:
>
> "Using a passphrase also disables the ability to change the server's
>SSL configuration without a server restart."
>
> But as of pg11 we have ssl_passphrase_c
On 4/24/19 4:54 AM, Peter Eisentraut wrote:
> On 2019-04-23 18:53, Tom Lane wrote:
>> Peter Eisentraut writes:
>>> On 2019-04-23 16:15, Joe Conway wrote:
I don't think so. Not sure if you have an account at Red Hat, but this
ticket covers it:
https://access.redhat.com/solutions/4819
On 2019-04-23 18:53, Tom Lane wrote:
> Peter Eisentraut writes:
>> On 2019-04-23 16:15, Joe Conway wrote:
>>> I don't think so. Not sure if you have an account at Red Hat, but this
>>> ticket covers it:
>>> https://access.redhat.com/solutions/48199
>
>> That discusses the equally-named export opt
