Re: documentation fix for SET ROLE

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: documentation fix for SET ROLE
Date: 2021-03-12 21:41:15
Message-ID: 5B3A2C16-8401-4E0F-B5FA-E04469F43F20@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/12/21, 11:14 AM, "Joe Conway" <mail(at)joeconway(dot)com> wrote:
> On 3/12/21 1:16 PM, Bossart, Nathan wrote:
>> My main goal of this thread is to get the RESET ROLE documentation
>> fixed. I don't have a terribly strong opinion on documenting these
>> special uses of "role". I lean in favor of adding it, but I wouldn't
>> be strongly opposed to simply leaving it out for now. But if we're
>> going to add it, I think we might as well add it everywhere.
>
>
> Looking back at the commit history it seems to me that this only works
> accidentally. Perhaps it would be best to fix RESET ROLE and be done with it.

That seems reasonable to me.

Nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-03-12 21:43:05 Re: pg_amcheck contrib application
Previous Message Tom Lane 2021-03-12 21:40:25 Re: [patch] [doc] Minor variable related cleanup and rewording of plpgsql docs