pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedStreaming Replication and Hash Indices
2+ messages / 2 participants
[nested] [flat]
* Streaming Replication and Hash Indices
@ 2016-01-18 12:15 Seb Mel <webmaster@mailz.de>
0 siblings, 1 reply; 2+ messages in thread
From: Seb Mel @ 2016-01-18 12:15 UTC (permalink / raw)
To: pgsql-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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Streaming Replication and Hash Indices
@ 2016-01-19 01:28 Bruce Momjian <bruce@momjian.us>
parent: Seb Mel <webmaster@mailz.de>
0 siblings, 0 replies; 2+ messages in thread
From: Bruce Momjian @ 2016-01-19 01:28 UTC (permalink / raw)
To: Seb Mel <webmaster@mailz.de>; +Cc: pgsql-docs
On Mon, Jan 18, 2016 at 01:15:28PM +0100, Seb Mel wrote:
> 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 :)!
We issue a warning on hash index creation in 9.5:
Issue a warning during the creation of <link
linkend="indexes-types">hash</> indexes because they are not
crash-safe (Bruce Momjian)
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2016-01-19 01:28 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-01-18 12:15 Streaming Replication and Hash Indices Seb Mel <webmaster@mailz.de>
2016-01-19 01:28 ` Bruce Momjian <bruce@momjian.us>
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