From: Seb Mel <webmaster@mailz.de>
To: pgsql-docs@postgresql.org
Subject: Streaming Replication and Hash Indices
Date: Mon, 18 Jan 2016 13:15:28 +0100
Message-ID: <17792594-F751-46ED-BFBD-7FDF9092A6FA@mailz.de> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
Hi list,
today i got bitten by the issue that streaming replication does not replicate "hash" indices as those changes are not written to WAL. That fact is documented here:
http://www.postgresql.org/docs/current/static/indexes-types.html
But i could not find that information anywhere else like:
https://wiki.postgresql.org/wiki/Streaming_Replication#Restrictions
or
http://www.postgresql.org/docs/current/static/warm-standby.html
I suppose it would be very helpful to add it there, as the usual policy for "corrupt slave data" is to recreate the slave from 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 :)!
Regards,
Seb
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: webmaster@mailz.de
Subject: Re: Streaming Replication and Hash Indices
In-Reply-To: <17792594-F751-46ED-BFBD-7FDF9092A6FA@mailz.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox