today i got bitten by the issue that streaming replication does not replicate "hash" indices as those changes are not
writtento WAL. That fact is documented here:
But i could not find that information anywhere else like:
I suppose it would be very helpful to add it there, as the usual policy for "corrupt slave data" is to recreate the
slavefrom a base_backup which would make you into thinking that the issue was fixed.
That is wrong though, as it will reappear after some time when the data in the table and the index diverge :)!
В списке pgsql-docs по дате сообщения: