On Mon, May 29, 2023 at 11:56:09PM -0500, Jaime Casanova wrote:
> try to update to v14.8 which has some fixes on it
Agreed about re-checking with 14.8. I'd be happy to look at the
report if there is a way to diagnose it, but there is no such evidence
at hand. A self-contained test case would be the best thing, of
course, if the problem still persists on your hand.
You may want to be careful in not providing production-sensitive data
on this mailing list as this is a public space.
--
Michael
