public inbox for [email protected]
help / color / mirror / Atom feedQuestion about role attributes docs
8+ messages / 5 participants
[nested] [flat]
* Question about role attributes docs
@ 2022-01-11 07:40 Shinya Kato <[email protected]>
2022-01-11 17:07 ` Re: Question about role attributes docs Laurenz Albe <[email protected]>
0 siblings, 1 reply; 8+ messages in thread
From: Shinya Kato @ 2022-01-11 07:40 UTC (permalink / raw)
To: [email protected]
Hi!
I have a question about the documentation on ROLE.
According to [1], INHERIT and BYPASSRLS can be specified when executing
the CREATE ROLE command. However, there is no such description in Role
Attributes in [2]. Are these concepts different from Role Attributes? Or
are they just not documented? If they need to be documented, I'll create
a patch.
[1] https://www.postgresql.org/docs/devel/sql-createrole.html
[2] https://www.postgresql.org/docs/devel/role-attributes.html
--
Regards,
--
Shinya Kato
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Question about role attributes docs
2022-01-11 07:40 Question about role attributes docs Shinya Kato <[email protected]>
@ 2022-01-11 17:07 ` Laurenz Albe <[email protected]>
2022-01-13 07:07 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
0 siblings, 1 reply; 8+ messages in thread
From: Laurenz Albe @ 2022-01-11 17:07 UTC (permalink / raw)
To: Shinya Kato <[email protected]>; [email protected]
On Tue, 2022-01-11 at 16:40 +0900, Shinya Kato wrote:
> I have a question about the documentation on ROLE.
>
> According to [1], INHERIT and BYPASSRLS can be specified when executing
> the CREATE ROLE command. However, there is no such description in Role
> Attributes in [2]. Are these concepts different from Role Attributes? Or
> are they just not documented? If they need to be documented, I'll create
> a patch.
>
> [1] https://www.postgresql.org/docs/devel/sql-createrole.html
> [2] https://www.postgresql.org/docs/devel/role-attributes.html
I think that is indeed an omission, and adding documentation would be a
good idea. On the other hand, a lot of that information is more or less
a duplicate of the CREATE ROLE documentation. I wonder if the latter
page could be removed altogether.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Question about role attributes docs
2022-01-11 07:40 Question about role attributes docs Shinya Kato <[email protected]>
2022-01-11 17:07 ` Re: Question about role attributes docs Laurenz Albe <[email protected]>
@ 2022-01-13 07:07 ` Shinya Kato <[email protected]>
2022-02-15 21:39 ` Re: Question about role attributes docs Swaha Miller <[email protected]>
0 siblings, 1 reply; 8+ messages in thread
From: Shinya Kato @ 2022-01-13 07:07 UTC (permalink / raw)
To: Laurenz Albe <[email protected]>; +Cc: [email protected]
On 2022-01-12 02:07, Laurenz Albe wrote:
> On Tue, 2022-01-11 at 16:40 +0900, Shinya Kato wrote:
>> I have a question about the documentation on ROLE.
>>
>> According to [1], INHERIT and BYPASSRLS can be specified when
>> executing
>> the CREATE ROLE command. However, there is no such description in Role
>> Attributes in [2]. Are these concepts different from Role Attributes?
>> Or
>> are they just not documented? If they need to be documented, I'll
>> create
>> a patch.
>>
>> [1] https://www.postgresql.org/docs/devel/sql-createrole.html
>> [2] https://www.postgresql.org/docs/devel/role-attributes.html
>
> I think that is indeed an omission, and adding documentation would be a
> good idea.
Thanks! I created the patch, and attached it.
> On the other hand, a lot of that information is more or less
> a duplicate of the CREATE ROLE documentation. I wonder if the latter
> page could be removed altogether.
I think there is certainly a lot of overlap. However, I think that the
SQL commands page and the database roles page should exist separately,
and should be maintained as they are because there are parts that do not
overlap (for example, IN ROLE and ADMIN).
--
Regards,
--
Shinya Kato
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
Attachments:
[text/x-diff] add-role-attributes-to-docs.patch (2.1K, 2-add-role-attributes-to-docs.patch)
download | inline diff:
diff --git a/doc/src/sgml/user-manag.sgml b/doc/src/sgml/user-manag.sgml
index 9067be1d9c..cf6adb3436 100644
--- a/doc/src/sgml/user-manag.sgml
+++ b/doc/src/sgml/user-manag.sgml
@@ -236,6 +236,42 @@ CREATE USER <replaceable>name</replaceable>;
</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term>inheritance of privileges<indexterm><primary>role</primary><secondary>privilege to inherit</secondary></indexterm></term>
+ <listitem>
+ <para>
+ A role is needed to permission to inherit privileges of roles it is a member of.
+ (except for superusers, since those bypass all permission checks).
+ If not specified, <literal>INHERIT</literal> is the default, so to create such a role, use either:
+<programlisting>
+CREATE ROLE <replaceable>name</replaceable> INHERIT;
+CREATE ROLE <replaceable>name</replaceable>;
+</programlisting>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>bypass row-level security<indexterm><primary>role</primary><secondary>privilege to bypass</secondary></indexterm></term>
+ <listitem>
+ <para>
+ A role must be explicitly given permission to bypass row-level security (RLS) policy.
+ (except for superusers, since those bypass all permission checks).
+ To create such a role, use <literal>CREATE ROLE <replaceable>name</replaceable> BYPASSRLS</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>connection limit<indexterm><primary>role</primary><secondary>privilege to limit connection</secondary></indexterm></term>
+ <listitem>
+ <para>
+ Connection limit can specify how many concurrent connections a role can make.
+ -1 (the default) means no limit. To create such a role, use <literal>CREATE ROLE <replaceable>name</replaceable> CONNECTION LIMIT<replaceable> connlimit</replaceable> LOGIN</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
A role's attributes can be modified after creation with
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Question about role attributes docs
2022-01-11 07:40 Question about role attributes docs Shinya Kato <[email protected]>
2022-01-11 17:07 ` Re: Question about role attributes docs Laurenz Albe <[email protected]>
2022-01-13 07:07 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
@ 2022-02-15 21:39 ` Swaha Miller <[email protected]>
2022-03-17 08:56 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
0 siblings, 1 reply; 8+ messages in thread
From: Swaha Miller @ 2022-02-15 21:39 UTC (permalink / raw)
To: Shinya Kato <[email protected]>; +Cc: Laurenz Albe <[email protected]>; [email protected]
On Tue, Feb 15, 2022 at 1:32 PM Shinya Kato <[email protected]>
wrote:
> On 2022-01-12 02:07, Laurenz Albe wrote:
> > On Tue, 2022-01-11 at 16:40 +0900, Shinya Kato wrote:
> >> I have a question about the documentation on ROLE.
> >>
> >> According to [1], INHERIT and BYPASSRLS can be specified when
> >> executing
> >> the CREATE ROLE command. However, there is no such description in Role
> >> Attributes in [2]. Are these concepts different from Role Attributes?
> >> Or
> >> are they just not documented? If they need to be documented, I'll
> >> create
> >> a patch.
> >>
> >> [1] https://www.postgresql.org/docs/devel/sql-createrole.html
> >> [2] https://www.postgresql.org/docs/devel/role-attributes.html
> >
> > I think that is indeed an omission, and adding documentation would be a
> > good idea.
> Thanks! I created the patch, and attached it.
>
> > On the other hand, a lot of that information is more or less
> > a duplicate of the CREATE ROLE documentation. I wonder if the latter
> > page could be removed altogether.
> I think there is certainly a lot of overlap. However, I think that the
> SQL commands page and the database roles page should exist separately,
> and should be maintained as they are because there are parts that do not
> overlap (for example, IN ROLE and ADMIN).
>
> --
> Regards,
>
> --
> Shinya Kato
> Advanced Computing Technology Center
> Research and Development Headquarters
> NTT DATA CORPORATION
May I suggest replacing the following verbiage in your patch
+ A role is needed to permission to inherit privileges of roles it
is a member of.
+ (except for superusers, since those bypass all permission checks).
+ If not specified, <literal>INHERIT</literal> is the default, so to
create such a role, use either:
with clearer wording such as the following:
A role can explicitly be restricted at time of creation from inheriting
privileges of
roles it is a member of (except for superusers, since those bypass all
permission checks.)
Restricting privileges is done by the <literal>NOINHERIT</literal> option.
If no option is specified, <literal>INHERIT</literal> is the default. So to
create a role that inherits
privileges, use either:
Regards,
Swaha Miller
Amazon Web Services
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Question about role attributes docs
2022-01-11 07:40 Question about role attributes docs Shinya Kato <[email protected]>
2022-01-11 17:07 ` Re: Question about role attributes docs Laurenz Albe <[email protected]>
2022-01-13 07:07 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
2022-02-15 21:39 ` Re: Question about role attributes docs Swaha Miller <[email protected]>
@ 2022-03-17 08:56 ` Shinya Kato <[email protected]>
2022-07-22 15:35 ` Re: Question about role attributes docs Fujii Masao <[email protected]>
0 siblings, 1 reply; 8+ messages in thread
From: Shinya Kato @ 2022-03-17 08:56 UTC (permalink / raw)
To: Swaha Miller <[email protected]>; +Cc: Laurenz Albe <[email protected]>; [email protected]
On 2022-02-16 06:39, Swaha Miller wrote:
> On Tue, Feb 15, 2022 at 1:32 PM Shinya Kato
> <[email protected]> wrote:
>
>> On 2022-01-12 02:07, Laurenz Albe wrote:
>>> On Tue, 2022-01-11 at 16:40 +0900, Shinya Kato wrote:
>>>> I have a question about the documentation on ROLE.
>>>>
>>>> According to [1], INHERIT and BYPASSRLS can be specified when
>>>> executing
>>>> the CREATE ROLE command. However, there is no such description in
>> Role
>>>> Attributes in [2]. Are these concepts different from Role
>> Attributes?
>>>> Or
>>>> are they just not documented? If they need to be documented, I'll
>>
>>>> create
>>>> a patch.
>>>>
>>>> [1] https://www.postgresql.org/docs/devel/sql-createrole.html
>>>> [2] https://www.postgresql.org/docs/devel/role-attributes.html
>>>
>>> I think that is indeed an omission, and adding documentation would
>> be a
>>> good idea.
>> Thanks! I created the patch, and attached it.
>>
>>> On the other hand, a lot of that information is more or less
>>> a duplicate of the CREATE ROLE documentation. I wonder if the
>> latter
>>> page could be removed altogether.
>> I think there is certainly a lot of overlap. However, I think that
>> the
>> SQL commands page and the database roles page should exist
>> separately,
>> and should be maintained as they are because there are parts that do
>> not
>> overlap (for example, IN ROLE and ADMIN).
>>
>> --
>> Regards,
>>
>> --
>> Shinya Kato
>> Advanced Computing Technology Center
>> Research and Development Headquarters
>> NTT DATA CORPORATION
>
> May I suggest replacing the following verbiage in your patch
> + A role is needed to permission to inherit privileges of roles
> it is a member of.
> + (except for superusers, since those bypass all permission
> checks).
> + If not specified, <literal>INHERIT</literal> is the default,
> so to create such a role, use either:
>
> with clearer wording such as the following:
>
> A role can explicitly be restricted at time of creation from
> inheriting privileges of
> roles it is a member of (except for superusers, since those bypass all
> permission checks.)
> Restricting privileges is done by the <literal>NOINHERIT</literal>
> option.
> If no option is specified, <literal>INHERIT</literal> is the default.
> So to create a role that inherits
>
> privileges, use either:
>
> Regards,
>
> Swaha Miller
> Amazon Web Services
Thank you for the review, and sorry for late reply.
I fixed it.
--
Regards,
--
Shinya Kato
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
Attachments:
[text/x-diff] v2-add-role-attributes-to-docs.patch (2.2K, 2-v2-add-role-attributes-to-docs.patch)
download | inline diff:
diff --git a/doc/src/sgml/user-manag.sgml b/doc/src/sgml/user-manag.sgml
index 9067be1d9c..fb9f382c92 100644
--- a/doc/src/sgml/user-manag.sgml
+++ b/doc/src/sgml/user-manag.sgml
@@ -236,6 +236,44 @@ CREATE USER <replaceable>name</replaceable>;
</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term>inheritance of privileges<indexterm><primary>role</primary><secondary>privilege to inherit</secondary></indexterm></term>
+ <listitem>
+ <para>
+ A role can explicitly be restricted at time of creation from inheriting privileges of
+ roles it is a member of (except for superusers, since those bypass all permission checks.)
+ Restricting privileges is done by the <literal>NOINHERIT</literal> option.
+ If no option is specified, <literal>INHERIT</literal> is the default. So to create a role that inherits
+ privileges, use either:
+<programlisting>
+CREATE ROLE <replaceable>name</replaceable> INHERIT;
+CREATE ROLE <replaceable>name</replaceable>;
+</programlisting>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>bypass row-level security<indexterm><primary>role</primary><secondary>privilege to bypass</secondary></indexterm></term>
+ <listitem>
+ <para>
+ A role must be explicitly given permission to bypass row-level security (RLS) policy.
+ (except for superusers, since those bypass all permission checks).
+ To create such a role, use <literal>CREATE ROLE <replaceable>name</replaceable> BYPASSRLS</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>connection limit<indexterm><primary>role</primary><secondary>privilege to limit connection</secondary></indexterm></term>
+ <listitem>
+ <para>
+ Connection limit can specify how many concurrent connections a role can make.
+ -1 (the default) means no limit. To create such a role, use <literal>CREATE ROLE <replaceable>name</replaceable> CONNECTION LIMIT<replaceable> connlimit</replaceable> LOGIN</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
A role's attributes can be modified after creation with
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Question about role attributes docs
2022-01-11 07:40 Question about role attributes docs Shinya Kato <[email protected]>
2022-01-11 17:07 ` Re: Question about role attributes docs Laurenz Albe <[email protected]>
2022-01-13 07:07 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
2022-02-15 21:39 ` Re: Question about role attributes docs Swaha Miller <[email protected]>
2022-03-17 08:56 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
@ 2022-07-22 15:35 ` Fujii Masao <[email protected]>
2022-07-25 03:29 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
0 siblings, 1 reply; 8+ messages in thread
From: Fujii Masao @ 2022-07-22 15:35 UTC (permalink / raw)
To: Shinya Kato <[email protected]>; Swaha Miller <[email protected]>; +Cc: Laurenz Albe <[email protected]>; [email protected]
On 2022/03/17 17:56, Shinya Kato wrote:
> Thank you for the review, and sorry for late reply.
> I fixed it.
Thanks for updating the patch!
I found that the patch has two trailing whitespaces.
+ A role can explicitly be restricted at time of creation from inheriting privileges of
+ roles it is a member of (except for superusers, since those bypass all permission checks.)
+ Restricting privileges is done by the <literal>NOINHERIT</literal> option.
+ If no option is specified, <literal>INHERIT</literal> is the default. So to create a role that inherits
+ privileges, use either:
It sounds strange to me that restriction of inheritance is explained at the beginning. Instead, something like the following is more intuitive and easy-to-understand to users?
------------------------
A role is given permission to inherit the privileges of roles it is a member of, by default. However, to create a role without the permission, use CREATE ROLE name NOINHERIT.
------------------------
+ A role must be explicitly given permission to bypass row-level security (RLS) policy.
+ (except for superusers, since those bypass all permission checks).
Like CREATE ROLE docs does, isn't it better to add "every" just before "row-level"?
A dot just between "policy" and "(except" should be removed.
+ <term>bypass row-level security<indexterm><primary>role</primary><secondary>privilege to bypass</secondary></indexterm></term>
"bypass" should be "bypassing" or something because a noun is used for each entry title in other places?
+ To create such a role, use <literal>CREATE ROLE <replaceable>name</replaceable> BYPASSRLS</literal>.
Isn't it better to add "as a superuser" just after "BYPASSRLS</literal>" because only a superuser can create a new role having the BYPASSRLS attribute?
+ -1 (the default) means no limit. To create such a role, use <literal>CREATE ROLE <replaceable>name</replaceable> CONNECTION LIMIT<replaceable> connlimit</replaceable> LOGIN</literal>.
"To create such a role" sounds odd to me in this context. Instead, how about something like "Specify connection limit upon role creation with CREATE ROLE name CONNECTION LIMIT 'integer'."?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Question about role attributes docs
2022-01-11 07:40 Question about role attributes docs Shinya Kato <[email protected]>
2022-01-11 17:07 ` Re: Question about role attributes docs Laurenz Albe <[email protected]>
2022-01-13 07:07 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
2022-02-15 21:39 ` Re: Question about role attributes docs Swaha Miller <[email protected]>
2022-03-17 08:56 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
2022-07-22 15:35 ` Re: Question about role attributes docs Fujii Masao <[email protected]>
@ 2022-07-25 03:29 ` Shinya Kato <[email protected]>
2022-08-12 19:44 ` Re: Question about role attributes docs Bruce Momjian <[email protected]>
0 siblings, 1 reply; 8+ messages in thread
From: Shinya Kato @ 2022-07-25 03:29 UTC (permalink / raw)
To: Fujii Masao <[email protected]>; +Cc: Swaha Miller <[email protected]>; Laurenz Albe <[email protected]>; [email protected]
On 2022-07-23 00:35, Fujii Masao wrote:
> On 2022/03/17 17:56, Shinya Kato wrote:
>> Thank you for the review, and sorry for late reply.
>> I fixed it.
>
> Thanks for updating the patch!
Thank you for the review!
> I found that the patch has two trailing whitespaces.
Sorry, I fixed them.
> + A role can explicitly be restricted at time of creation from
> inheriting privileges of
> + roles it is a member of (except for superusers, since those
> bypass all permission checks.)
> + Restricting privileges is done by the
> <literal>NOINHERIT</literal> option.
> + If no option is specified, <literal>INHERIT</literal> is the
> default. So to create a role that inherits
> + privileges, use either:
>
> It sounds strange to me that restriction of inheritance is explained
> at the beginning. Instead, something like the following is more
> intuitive and easy-to-understand to users?
>
> ------------------------
> A role is given permission to inherit the privileges of roles it is a
> member of, by default. However, to create a role without the
> permission, use CREATE ROLE name NOINHERIT.
> ------------------------
>
> + A role must be explicitly given permission to bypass
> row-level security (RLS) policy.
> + (except for superusers, since those bypass all permission
> checks).
>
> Like CREATE ROLE docs does, isn't it better to add "every" just before
> "row-level"?
>
> A dot just between "policy" and "(except" should be removed.
>
> + <term>bypass row-level
> security<indexterm><primary>role</primary><secondary>privilege to
> bypass</secondary></indexterm></term>
>
> "bypass" should be "bypassing" or something because a noun is used for
> each entry title in other places?
>
> + To create such a role, use <literal>CREATE ROLE
> <replaceable>name</replaceable> BYPASSRLS</literal>.
>
> Isn't it better to add "as a superuser" just after
> "BYPASSRLS</literal>" because only a superuser can create a new role
> having the BYPASSRLS attribute?
>
> + -1 (the default) means no limit. To create such a role, use
> <literal>CREATE ROLE <replaceable>name</replaceable> CONNECTION
> LIMIT<replaceable> connlimit</replaceable> LOGIN</literal>.
>
> "To create such a role" sounds odd to me in this context. Instead, how
> about something like "Specify connection limit upon role creation with
> CREATE ROLE name CONNECTION LIMIT 'integer'."?
I agree with what you say. I fixed everything.
--
Regards,
--
Shinya Kato
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
Attachments:
[text/x-diff] v3-add-role-attributes-to-docs.patch (1.9K, 2-v3-add-role-attributes-to-docs.patch)
download | inline diff:
diff --git a/doc/src/sgml/user-manag.sgml b/doc/src/sgml/user-manag.sgml
index 6eaaaa36b8..54cb253d95 100644
--- a/doc/src/sgml/user-manag.sgml
+++ b/doc/src/sgml/user-manag.sgml
@@ -236,6 +236,39 @@ CREATE USER <replaceable>name</replaceable>;
</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term>inheritance of privileges<indexterm><primary>role</primary><secondary>privilege to inherit</secondary></indexterm></term>
+ <listitem>
+ <para>
+ A role is given permission to inherit the privileges of roles it is a
+ member of, by default. However, to create a role without the permission,
+ use <literal>CREATE ROLE <replaceable>name</replaceable> NOINHERIT</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>bypassing row-level security<indexterm><primary>role</primary><secondary>privilege to bypass</secondary></indexterm></term>
+ <listitem>
+ <para>
+ A role must be explicitly given permission to bypass every row-level security (RLS) policy
+ (except for superusers, since those bypass all permission checks).
+ To create such a role, use <literal>CREATE ROLE <replaceable>name</replaceable> BYPASSRLS</literal> as a superuser.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>connection limit<indexterm><primary>role</primary><secondary>privilege to limit connection</secondary></indexterm></term>
+ <listitem>
+ <para>
+ Connection limit can specify how many concurrent connections a role can make.
+ -1 (the default) means no limit. Specify connection limit upon role creation with
+ <literal>CREATE ROLE <replaceable>name</replaceable> CONNECTION LIMIT '<replaceable>integer</replaceable>'</literal>.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
A role's attributes can be modified after creation with
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Question about role attributes docs
2022-01-11 07:40 Question about role attributes docs Shinya Kato <[email protected]>
2022-01-11 17:07 ` Re: Question about role attributes docs Laurenz Albe <[email protected]>
2022-01-13 07:07 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
2022-02-15 21:39 ` Re: Question about role attributes docs Swaha Miller <[email protected]>
2022-03-17 08:56 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
2022-07-22 15:35 ` Re: Question about role attributes docs Fujii Masao <[email protected]>
2022-07-25 03:29 ` Re: Question about role attributes docs Shinya Kato <[email protected]>
@ 2022-08-12 19:44 ` Bruce Momjian <[email protected]>
0 siblings, 0 replies; 8+ messages in thread
From: Bruce Momjian @ 2022-08-12 19:44 UTC (permalink / raw)
To: Shinya Kato <[email protected]>; +Cc: Fujii Masao <[email protected]>; Swaha Miller <[email protected]>; Laurenz Albe <[email protected]>; [email protected]
On Mon, Jul 25, 2022 at 12:29:54PM +0900, Shinya Kato wrote:
> On 2022-07-23 00:35, Fujii Masao wrote:
> > On 2022/03/17 17:56, Shinya Kato wrote:
> > > Thank you for the review, and sorry for late reply.
> > > I fixed it.
> >
> > Thanks for updating the patch!
> Thank you for the review!
Patch applied back to PG 10. Commitfest status updated.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2022-08-12 19:44 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-01-11 07:40 Question about role attributes docs Shinya Kato <[email protected]>
2022-01-11 17:07 ` Laurenz Albe <[email protected]>
2022-01-13 07:07 ` Shinya Kato <[email protected]>
2022-02-15 21:39 ` Swaha Miller <[email protected]>
2022-03-17 08:56 ` Shinya Kato <[email protected]>
2022-07-22 15:35 ` Fujii Masao <[email protected]>
2022-07-25 03:29 ` Shinya Kato <[email protected]>
2022-08-12 19:44 ` Bruce Momjian <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox