Also I found this on postgresql website: http://www.postgresql.org/docs/9.0/static/indexes-types.html
*"Caution* Hash index operations are not presently WAL-logged, so hash indexes might need to be rebuilt with REINDEX after a database crash. They are also not replicated over streaming or file-based replication. For these reasons, hash index use is presently discouraged. " On Tue, Mar 22, 2011 at 4:59 PM, Armin Nesiren <[email protected]>wrote: > But, what am I doing wrong then. > When I insert something in master node, and after that take select, I see > my record. > > On slave, when using index I can not see exact record, and without using > index, record is there. > I have configured streaming replication. > > > On Tue, Mar 22, 2011 at 4:48 PM, Simon Riggs <[email protected]>wrote: > >> On Tue, Mar 22, 2011 at 3:04 PM, Guillaume Lelarge >> <[email protected]> wrote: >> > Le 22/03/2011 15:25, Armin Nesiren a écrit : >> >> I have problem reading from slave node values that is indexed with hash >> >> index. >> >> >> >> Does pgpool replicate hash indexes? Is there any special configuration >> for >> >> hash index? >> >> >> > >> > If you use pgpool replication system, you should have no issue with hash >> > index (or any other kind of index). >> > >> > The only replication system that has issue with hash index, AFAIK, is >> > the wal shipping of PostgreSQL. >> > >> >> Hash indexes aren't crash safe, meaning they become corrupt if the >> database crashes or someone does an immediate shutdown. >> >> You shouldn't be mixing high availability and hash indexes, whatever >> the weather. >> >> -- >> Simon Riggs http://www.2ndQuadrant.com/ >> PostgreSQL Development, 24x7 Support, Training & Services >> > > > > -- > Armin > -- Armin
_______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
