Horton

Re: If a row-level security policy contains a set returning function, pg_dump returns an incorrect serialization of that policy if the return type of the function was altered

Dean Rasheed <dean.a.rasheed@gmail.com>

View thread View on postgr.es
From: Dean Rasheed <dean.a.rasheed@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Timo Stolz <timo.stolz@nullachtvierzehn.de>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Jonas Reinsch <jonas.reinsch@pitchview.de>, Laura Schlimmer <laura.schlimmer@pitchview.de>
Date: 2022-07-21T21:27:38Z
Lists: pgsql-bugs 
On Thu, 21 Jul 2022 at 20:19, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I wrote:
> > I think I'll go take a look at the missing-dependency aspect now.
> > I realized from checking the commit log that we've been putting
> > off doing that since 2014, if not before.  Really should fix it.
>
> Here's a proposed patch for that.  I wouldn't consider pushing this
> into released branches, but maybe it's not too late for v15?
>

That looks reasonable to me. It covers all the cases I could think of
to try, and I can't see any loopholes. +1 for applying it to v15.

Regards,
Dean

Commits

  1. Close old gap in dependency checks for functions returning composite.

  2. Fix ruleutils issues with dropped cols in functions-returning-composite.