On Mon, Jul 24, 2023 at 08:21:54PM -0400, Tom Lane wrote:
> Yeah, I dithered about that. I felt like removing it only to put it
> back later would be silly, but then again maybe there won't ever be
> a need to put it back. I'm OK with removing it if there's not
> objections.
Seeing what this code does, the odds of needing an err_msg seem rather
low to me, so I would just remove it for now for the sake of clarity.
It can always be added later if need be.
--
Michael