Re: [BUGS] BUG #8056: postgres forgets hstore over time
You mean by running current_schemas(true) on that session? So far I have remade the hstore functions into this and it seems to be working for now: (But this happens randomly after time so it might take a day or 2 to be sure this addresses the issue) CREATE OR REPLACE FUNCTION accounts.myhstore_merge(myh hstore, mytext text[]) RETURNS hstore AS $BODY$BEGIN SET search_path TO public; RETURN myh || hstore(mytext); END;$BODY$ LANGUAGE plpgsql VOLATILE COST 100; From: Dickson S. Guedes To: knowze...@yahoo.com Cc: pgsql-bugs@postgresql.org Sent: Wednesday, April 10, 2013 7:19 AM Subject: Re: [BUGS] BUG #8056: postgres forgets hstore over time 2013/4/9 : > The following bug has been logged on the website: > > Bug reference: 8056 > Logged by: Eugene > Email address: knowze...@yahoo.com > PostgreSQL version: 9.2.1 Please update your Postgres to 9.2.4. > I have hstore installed on my server and it works fine. But sometimes > postgres would give me errors such as: > > type "hstore" does not exist Did you check search_path? Compare search_path between sessions that are getting error and see if hstore type/functions are reached through it. []s -- Dickson S. Guedes mail/xmpp: gue...@guedesoft.net - skype: guediz http://github.com/guedes - http://guedesoft.net http://www.postgresql.org.br
Re: [BUGS] BUG #8056: postgres forgets hstore over time
Ok, after making my own functions and putting: SET search_path TO public; On top, the errors seemed to have stopped. So it seems like this is an issue with the search_path being forgotten. From: Dickson S. Guedes To: knowze...@yahoo.com Cc: pgsql-bugs@postgresql.org Sent: Wednesday, April 10, 2013 7:19 AM Subject: Re: [BUGS] BUG #8056: postgres forgets hstore over time 2013/4/9 : > The following bug has been logged on the website: > > Bug reference: 8056 > Logged by: Eugene > Email address: knowze...@yahoo.com > PostgreSQL version: 9.2.1 Please update your Postgres to 9.2.4. > I have hstore installed on my server and it works fine. But sometimes > postgres would give me errors such as: > > type "hstore" does not exist Did you check search_path? Compare search_path between sessions that are getting error and see if hstore type/functions are reached through it. []s -- Dickson S. Guedes mail/xmpp: gue...@guedesoft.net - skype: guediz http://github.com/guedes - http://guedesoft.net http://www.postgresql.org.br
