Try SHOW search_path; On both the good and bad connection. Is it possible you have some code setting it and leaving it set incorrectly?
-- greg On 12 Oct 2013 23:17, "John R Pierce" <pie...@hogranch.com> wrote: > On 10/9/2013 10:35 AM, nbudu...@gmail.com wrote: > >> Basically, at some point a query, update or insert will not work and >> complain about a table not existing, but that table was used without any >> issue previously. Closing the running connection to the database and >> reconnecting make that error disappear. Two concurrent connections (one >> from >> a console and another from the app) could be contradicting themselves, one >> giving the error and the other not. >> > > > that sounds like a hardware/platform problem to me more than anything. > maybe in memory cache is getting corrupted or something? > > > > -- > john r pierce 37N 122W > somewhere on the middle of the left coast > > > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/**mailpref/pgsql-bugs<http://www.postgresql.org/mailpref/pgsql-bugs> >
