Re: Avoid orphaned objects dependencies, take 3

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com>, Roman Eskin <r(dot)eskin(at)arenadata(dot)io>, Michael Paquier <michael(at)paquier(dot)xyz>, Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Avoid orphaned objects dependencies, take 3
Date: 2026-06-08 21:55:19
Message-ID: 71eb9a8835a28165939da567a9d649fe6d21bfa7.camel@j-davis.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2026-06-05 at 13:09 +0000, Bertrand Drouvot wrote:
> the current patch

/*
* Look up a tracked aclcheck entry for the given object.
* Returns true if found, filling in roleId, mode, and inval_count.
* Searches from the end to find the most recent check (the one with
the
* freshest inval_count).

What if two tracked ACL checks had different modes? Don't you need to
do both checks or somehow combine the modes in the tracking entry?

(I'm not sure if this is a practical problem or not.)

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-06-08 22:16:46 Re: Add pattern matching support for LISTEN/NOTIFY channels
Previous Message Matheus Alcantara 2026-06-08 21:55:12 Re: Add pattern matching support for LISTEN/NOTIFY channels