Bruce Momjian wrote
> Now that we have the create hash index warning in 9.5, I realized that
> we don't warn about hash indexes with PITR, only crash recovery and
> streaming. This patch fixes that.
>
> Is the wording "cannot be used" too vague. The CREATE INDEX manual
> page has the words "give wrong answers to queries", which might be
> better, but is kind of long for an error message. Suggestions?
Something like the following is more specific without being more wordy:
"hash indexes are not WAL-logged: they are corrupted during recovery and
changes do not replicate to standby servers."
The question is whether we explain the implications of not being WAL-logged
in an error message or simply state the fact and let the documentation
explain the hazards - basically just output:
"hash indexes are not WAL-logged and their use is discouraged"
David J.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Hash-index-creation-warning-tp5823443p5823445.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.