Postgres Pro
Downloads
Home   >   mailing lists

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 - Mailing list pgsql-bugs

From Dean Rasheed
Subject 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
Date
Msg-id CAEZATCUJk88LWb5VNaW4qz6u2NgL1wvJQEHg=jJ4LK8kV-299A@mail.gmail.com
Whole thread Raw
In response to 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  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses 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
List pgsql-bugs
Tree view 
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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: 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
Next
From: Marco Boeringa
Date:
Subject: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?