PG Doc comments form writes:
> I have checked this for CREATEROLE and this role attribute is definitely
> inheritable.
Does not look like that to me:
regression=# create user alice createrole;
CREATE ROLE
regression=# create user bob;
CREATE ROLE
regression=# \c - alice
You are now connected to
PG Doc comments form writes:
> In section #FUNCTIONS-COMPARISONS-IN-SCALAR operator IN is described as a
> expression for scalars, and as a shorthand notation for a combination of
> operators || and =
> In section #COMPOSITE-TYPE-COMPARISON described extension, to use operators
> with a records,
"David G. Johnston" writes:
> On Mon, Jul 17, 2023 at 7:45 PM Curt Kolovson wrote:
>> I’d vote for showing both (with RETURNING and without), since without it
>> the second argument to SPI_exec has no effect in this example, which may
>> not be obvious. That seems to be one of the subtle points i
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/role-membership.html
Description:
Regarding this paragraph: "The role attributes LOGIN, SUPERUSER, CREATEDB,
and CREATEROLE can be thought of as special privileges, but they are never
inhe
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/functions-comparisons.html
Description:
In section #FUNCTIONS-COMPARISONS-IN-SCALAR operator IN is described as a
expression for scalars, and as a shorthand notation for a combination of
o
