The logs that were printed by Postgres
when enforcing deferred unique indexes were misleading.
This change should make it easier to understand or investigate
when users see the `waits for ShareLock` log entry
---
doc/src/sgml/mvcc.sgml | 5 +
1 file changed, 5 insertions(+)
diff --git a/doc/
Hello
I had a production incident a few weeks ago while using deferred indexes, where
the Postgres docs lead me down the wrong path of investigation due to missing
details. Specifically, the docs implied that a `ShareLock` was only acquired
when creating indexes, but only after looking at the c
