Re: updates for handling optional argument in system functions - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: updates for handling optional argument in system functions
Date
Msg-id CAHGQGwEx=jiyoJmkb5EaTrq=oMLFpCC_tiso0PkMAGY_4UqSrA@mail.gmail.com
Whole thread
In response to Re: updates for handling optional argument in system functions  ("Tristan Partin" <tristan@partin.io>)
Responses Re: updates for handling optional argument in system functions
List pgsql-hackers
On Fri, Jun 19, 2026 at 1:50 AM Tristan Partin <tristan@partin.io> wrote:
> > Oops, v8.1 attached to correct that white space.
>
> Patches look great Mark!

Some patches no longer apply cleanly on HEAD, so they'll need to be rebased.

I have one question, though.

Suppose a user executes GRANT or REVOKE on pg_get_ruledef(oid), then
creates a dump with pg_dump. If that dump is restored into a newer
server where these patches have been applied, the restore would fail
because pg_get_ruledef(oid) no longer exists.

Is that acceptable (this means that users need to handle the restore
failure), or should pg_dump handle this case specially?

I suspect we've had similar situations before when system functions
changed between major versions, and I don't recall adding special
handling to pg_dump... Thought?

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Florin Irion
Date:
Subject: Re: psql tab completion for user functions and if explicitly required also "pg_"
Next
From: Tom Lane
Date:
Subject: Re: Schema-qualify the equality operator when deparsing NULLIF/IS DISTINCT FROM