Re: New default role- 'pg_read_all_data'

From: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
To: Stephen Frost <sfrost(at)snowman(dot)net>, Georgios Kokolatos <gkokolatos(at)protonmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: New default role- 'pg_read_all_data'
Date: 2020-11-23 22:08:35
Message-ID: 5a3e197e-3f6c-50e4-9774-c6b82b7151f1@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 29.10.2020 17:19, Stephen Frost wrote:
> Greetings,
>
> * Georgios Kokolatos (gkokolatos(at)protonmail(dot)com) wrote:
>> this patch is in "Ready for committer" state and the Cfbot is happy.
> Glad that's still the case. :)
>
>> Is there any committer that is available for taking a look at it?
> If there aren't any objections or further comments, I'll take another
> look through it and will commit it during the upcoming CF.
>
> Thanks!
>
> Stephen

CFM reminder. Just in case you forgot about this thread)
The commitfest is heading to the end. And there was a plenty of time for
anyone to object.

--
Anastasia Lubennikova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-11-23 22:10:30 Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)
Previous Message Tom Lane 2020-11-23 22:02:55 Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)