Request a Demo
Home   >   mailing lists

Re: Avoid orphaned objects dependencies, take 3 - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Avoid orphaned objects dependencies, take 3
Date
Msg-id ac52a6aa6be9ccf5cf43c44d009b6e2aa7e2c93d.camel@j-davis.com
Whole thread
In response to Re: Avoid orphaned objects dependencies, take 3  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
Responses Re: Avoid orphaned objects dependencies, take 3
List pgsql-hackers
Tree view 
On Tue, 2026-06-16 at 10:09 +0000, Bertrand Drouvot wrote:
> 0002: fixes it by moving aclcheck_track_record() to after the
> permission check
> succeeds in object_aclcheck_ext() and pg_class_aclcheck_ext().
> Indeed, there is
> no need to track failed permission checks.

IIUC, this is necessary for correctness. If an ACL failure doesn't
cause a transaction abort, then there's a danger that we cause the
transaction to fail that should have succeeded.

So the ACL tracking needs to be precise: we can't track an ACL check
unless a failure always causes transaction abort; and we must track an
ACL check if it would cause a transaction abort. Right?

Regards,
    Jeff Davis

pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: use of SPI by postgresImportForeignStatistics
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Fix segmentation fault and infinite loop in jsonb_{plperl,plpython}