grants files - Search results in mailing lists

2025-04-04 13:04:31 | pgsql: Extend ALTER DEFAULT PRIVILEGES to define default privileges for (Fujii Masao)

grant privileges to users other than the owner, permissions had to be manually assigned each time a large object was created, which was inconvenient. This commit extends ALTER DEFAULT PRIVILEGES to allow defining default access

2025-03-28 01:13:28 | pgsql: Fix guc_malloc calls for consistency and OOM checks (Daniel Gustafsson)

grant down to v16 and the fix to check_synchronized_standby_slots down to v17 where they were introduced. Author: Daniel Gustafsson Reported-by: Nikita Reviewed-by: Tom Lane Bug: #18845 Discussion

2025-03-28 01:13:04 | pgsql: Fix guc_malloc calls for consistency and OOM checks (Daniel Gustafsson)

grant down to v16 and the fix to check_synchronized_standby_slots down to v17 where they were introduced. Author: Daniel Gustafsson Reported-by: Nikita Reviewed-by: Tom Lane Bug: #18845 Discussion

2025-03-28 01:12:36 | pgsql: Fix guc_malloc calls for consistency and OOM checks (Daniel Gustafsson)

grant down to v16 and the fix to check_synchronized_standby_slots down to v17 where they were introduced. Author: Daniel Gustafsson Reported-by: Nikita Reviewed-by: Tom Lane Bug: #18845 Discussion

2025-02-22 01:07:09 | pgsql: Avoid race condition between "GRANT role" and "DROP ROLE". (Tom Lane)

granted role, since we're presumably about to drop it and besides we're removing all reasons why it'd matter to be a member of it. (One could argue that this makes DropRole

2025-02-21 21:37:37 | pgsql: Fix pg_dumpall to cope with dangling OIDs in pg_auth_members. (Tom Lane)

GRANTED BY clause. I left that behavior as-is, although it's somewhat inconsistent with the behavior of later branches. Reported-by: Virender Singla Discussion: https:///m/CAM6Zo8woa62ZFHtMKox6a4jb8qQ=w87R2L0K8347iE-juQL2EA@mail.gmail.com Backpatch-through: 13 Branch ------ master Details

2025-02-21 21:37:37 | pgsql: Fix pg_dumpall to cope with dangling OIDs in pg_auth_members. (Tom Lane)

GRANTED BY clause. I left that behavior as-is, although it's somewhat inconsistent with the behavior of later branches. Reported-by: Virender Singla Discussion: https:///m/CAM6Zo8woa62ZFHtMKox6a4jb8qQ=w87R2L0K8347iE-juQL2EA@mail.gmail.com Backpatch-through: 13 Branch ------ REL_17_STABLE

2025-02-21 21:37:37 | pgsql: Fix pg_dumpall to cope with dangling OIDs in pg_auth_members. (Tom Lane)

GRANTED BY clause. I left that behavior as-is, although it's somewhat inconsistent with the behavior of later branches. Reported-by: Virender Singla Discussion: https:///m/CAM6Zo8woa62ZFHtMKox6a4jb8qQ=w87R2L0K8347iE-juQL2EA@mail.gmail.com Backpatch-through: 13 Branch ------ REL_15_STABLE

2025-02-21 21:37:37 | pgsql: Fix pg_dumpall to cope with dangling OIDs in pg_auth_members. (Tom Lane)

GRANTED BY clause. I left that behavior as-is, although it's somewhat inconsistent with the behavior of later branches. Reported-by: Virender Singla Discussion: https:///m/CAM6Zo8woa62ZFHtMKox6a4jb8qQ=w87R2L0K8347iE-juQL2EA@mail.gmail.com Backpatch-through: 13 Branch ------ REL_16_STABLE

2025-02-21 21:37:37 | pgsql: Fix pg_dumpall to cope with dangling OIDs in pg_auth_members. (Tom Lane)

GRANTED BY clause. I left that behavior as-is, although it's somewhat inconsistent with the behavior of later branches. Reported-by: Virender Singla Discussion: https:///m/CAM6Zo8woa62ZFHtMKox6a4jb8qQ=w87R2L0K8347iE-juQL2EA@mail.gmail.com Backpatch-through: 13 Branch ------ REL_13_STABLE

2025-02-21 21:37:37 | pgsql: Fix pg_dumpall to cope with dangling OIDs in pg_auth_members. (Tom Lane)

GRANTED BY clause. I left that behavior as-is, although it's somewhat inconsistent with the behavior of later branches. Reported-by: Virender Singla Discussion: https:///m/CAM6Zo8woa62ZFHtMKox6a4jb8qQ=w87R2L0K8347iE-juQL2EA@mail.gmail.com Backpatch-through: 13 Branch ------ REL_14_STABLE

2025-02-20 18:47:40 | pgsql: Add support for OAUTHBEARER SASL mechanism (Daniel Gustafsson)

Grants, RFC 8628. In order to use this there is a new pg_hba auth method called oauth. When speaking to a OAuth- enabled server, it looks a bit like this: $ psql 'host=example

2024-12-28 18:21:31 | pgsql: In REASSIGN OWNED of a database, lock the tuple as mandated. (Noah Misch)

GRANT, implement this by following the locking protocol for any catalog subject to the generic AlterObjectOwner_internal(). It would suffice to do this for IsInplaceUpdateOid() catalogs only. Back-patch to v13 (all supported versions). Kirill

2024-12-28 18:21:31 | pgsql: In REASSIGN OWNED of a database, lock the tuple as mandated. (Noah Misch)

GRANT, implement this by following the locking protocol for any catalog subject to the generic AlterObjectOwner_internal(). It would suffice to do this for IsInplaceUpdateOid() catalogs only. Back-patch to v13 (all supported versions). Kirill

2024-12-28 18:21:31 | pgsql: In REASSIGN OWNED of a database, lock the tuple as mandated. (Noah Misch)

GRANT, implement this by following the locking protocol for any catalog subject to the generic AlterObjectOwner_internal(). It would suffice to do this for IsInplaceUpdateOid() catalogs only. Back-patch to v13 (all supported versions). Kirill