On Tue, 2024-03-12 at 16:05 -0500, Nathan Bossart wrote: > It's easy enough to resolve this inconsistency by sending > down the parent OID when recursing to a TOAST table and using that > for the > privilege checks. AFAICT this avoids any kind of cache lookup > hazards > because we hold a session lock on the main relation in this case. > I've > done this in the attached v2.
Looks good to me. Thank you for expanding on the comment, as well.
Regards,
Jeff Davis
