Re: refactor ownercheck and aclcheck functions

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: refactor ownercheck and aclcheck functions
Date: 2022-11-09 18:12:36
Message-ID: CADkLM=e5+TP6_07Jm6tJhJ8jUrApE+8YH2dc4g=ZcZFoPxk1=A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> After considering this again, I decided to brute-force this and get rid
> of all the trivial wrapper functions and also several of the special
> cases. That way, there is less confusion at the call sites about why
> this or that style is used in a particular case. Also, it now makes
> sure you can't accidentally use the generic functions when a particular
> one should be used.
>

+1

However, the aclcheck patch isn't applying for me now. That patch modifies
37 files, so it's hard to say just which commit conflicts.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Verite 2022-11-09 19:10:34 Re: psql: Add command to use extended query protocol
Previous Message Sandro Santilli 2022-11-09 17:53:52 Re: [PATCH] Support % wildcard in extension upgrade filenames