public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Noah Misch <[email protected]>
Cc: [email protected]
Subject: Re: PROPERTY GRAPH pg_dump ACL minimization
Date: Mon, 29 Jun 2026 23:11:01 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
Noah Misch <[email protected]> writes:
> Most of the patch bulk (modest as it is) exists to keep support for dumping
> from beta1. I'm not sure whether it was worth bothering. Breaking dump from
> a beta is without precedent known to me, so I just erred on the side of not
> breaking it. If we were to decide pg_dump could drop support for betas, I'd
> be fine with that.
> This entails a catversion bump on the v19 branch.
Those points are not unrelated. If you bump catversion then beta
testers must use pg_upgrade to get from beta1 to beta2, so you should
not drop support for dumping from beta1.
I could agree with dropping that support after beta2, though. That'd
imply having to update via beta2 to beta3 or later, but I doubt those
hardy enough to test beta1 would have a problem with that.
> If the master branch
> already has a post-branch catversion bump by then, the two catversions should
> remain distinct. I'll use yyyymmdd1 for v19 and yyyymmdd2 for master.
Check.
(I didn't read the patch, just responded to your commentary.)
regards, tom lane
view thread (11+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: PROPERTY GRAPH pg_dump ACL minimization
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox