| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PROPERTY GRAPH pg_dump ACL minimization |
| Date: | 2026-06-30 03:11:01 |
| Message-ID: | 2453089.1782789061@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Noah Misch <noah(at)leadboat(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Xuneng Zhou | 2026-06-30 03:14:54 | Re: Deadlock detector fails to activate on a hot standby replica |
| Previous Message | Noah Misch | 2026-06-30 02:33:08 | PROPERTY GRAPH pg_dump ACL minimization |