| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: Draft back-branch release notes are up |
| Date: | 2026-11-08 16:04:33 |
| Message-ID: | 2114848.1794153873@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> writes:
> [ assorted comments ]
Thanks for the review! I adopted your changes, except for
> 700b422af7e says the release note should mention more details:
> It's probably unlikely that people have commonly done this, but the
> release notes may wish to note that people should check if this has
> happened to them...
Yeah, I did read that text, and thought for a bit about how much of it
to include. The test query alone would have been fine, but without a
straightforward repair recipe, I'm not sure how useful it is. I don't
want to expend a large amount of note space on a problem that likely
affects very few people. Maybe we could stop at offering the ALTER
TABLE commands, and leave people to cope with finding any NULLs on
their own?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-11-08 16:06:40 | Re: Draft back-branch release notes are up |
| Previous Message | David G. Johnston | 2026-11-08 15:46:24 | Re: First draft of PG 19 release notes |