Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aLL64-00059M-Dq for pgsql-docs@arkaria.postgresql.org; Tue, 19 Jan 2016 01:28:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aLL63-0004vj-S2 for pgsql-docs@arkaria.postgresql.org; Tue, 19 Jan 2016 01:28:35 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aLL63-0004vY-CG for pgsql-docs@postgresql.org; Tue, 19 Jan 2016 01:28:35 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aLL5v-0000rT-SA for pgsql-docs@postgresql.org; Tue, 19 Jan 2016 01:28:34 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1aLL5t-0007eJ-R8; Mon, 18 Jan 2016 20:28:25 -0500 Date: Mon, 18 Jan 2016 20:28:25 -0500 From: Bruce Momjian To: Seb Mel Cc: pgsql-docs@postgresql.org Subject: Re: Streaming Replication and Hash Indices Message-ID: <20160119012825.GV31313@momjian.us> References: <17792594-F751-46ED-BFBD-7FDF9092A6FA@mailz.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17792594-F751-46ED-BFBD-7FDF9092A6FA@mailz.de> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org 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 hash indexes because they are not crash-safe (Bruce Momjian) -- Bruce Momjian 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