Re: Add has_large_object_privilege function

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Add has_large_object_privilege function
Date: 2024-09-26 08:16:07
Message-ID: ZvUYR0V0dzWaLnsV@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 13, 2024 at 03:56:11PM +0900, Yugo Nagata wrote:
> I confirmed the patches are committed in the master branch.
> Thank you!
>
> I've updated the commitfest status to "committed".

This patch has been committed as of 4eada203a5a8, and introduced this
block in pg_proc.dat:

{ oid => '4551', descr => 'user privilege on large objct by username, large object oid',
proname => 'has_largeobject_privilege', procost => '10', provolatile => 's',
prorettype => 'bool', proargtypes => 'name oid text',
prosrc => 'has_largeobject_privilege_name_id' },
{ oid => '4552', descr => 'current privilege on large objct by large object oid',
proname => 'has_largeobject_privilege', procost => '10', provolatile => 's',
prorettype => 'bool', proargtypes => 'oid text',
prosrc => 'has_largeobject_privilege_id' },
{ oid => '4553', descr => 'user privilege on large objct by user oid, large object oid',
proname => 'has_largeobject_privilege', procost => '10', provolatile => 's',
prorettype => 'bool', proargtypes => 'oid oid text',
prosrc => 'has_largeobject_privilege_id_id' },

This has a couple of mistakes:
- New functions introduced during a development cycle should use OIDs in
the range 8000-9999. See 98eab30b93d5, consisting of running
./unused_oids to get a random range.
- The function descriptions are inconsistent and have the three same
typos:
-- s/large objct/large object/.
-- s/current privilege/current user privilege/ for the second entry.

And while that's not mandatory for committers, I would apply a
reformat-dat-files while on it, to reduce some diffs I'm seeing.

This results in the attached that I'd like to apply to fix all that. It
needs a catalog version bump, of course.
--
Michael

Attachment Content-Type Size
0001-Fix-inconsistencies-with-catalog-data-of-new-LO-priv.patch text/x-diff 1.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-09-26 08:18:49 Re: pgsql: Implement pg_wal_replay_wait() stored procedure
Previous Message Denis Garsh 2024-09-26 07:54:16 Re: Add system column support to the USING clause