On Thu, 2020-12-03 at 13:14 -0500, Bruce Momjian wrote:
> How do we mandate that?  Just mention it in the docs and C comments?

Can't we just throw an error in pg_create_restore_point() if any high
bits are set? And perhaps error or Assert at a later point in case we
change the code in such a way as to let non-ASCII data in there.

This is probably the best approach, and it builds on your previous
patch (which already got consensus) rather than replacing it.

Regards,
        Jeff Davis




Reply via email to