To the best of my knowledge, the bug is not specific for PostgreSQL but happens with other databases as well.

I actually reported this issue a couple of days ago, please see: https://hibernate.atlassian.net/browse/HHH-15847?focusedCommentId=110550.

The bug is fixed in 6.2 which will be released soon.