From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | nbuduroi(at)gmail(dot)com, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #8515: Random 'relation "..." does not exist' |
Date: | 2013-10-14 02:56:37 |
Message-ID: | CAM-w4HPqPbJHrCvO0PhSXSVWWawBrbBE=gS-K61zESHu6b4PPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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" <pierce(at)hogranch(dot)com> wrote:
> On 10/9/2013 10:35 AM, nbuduroi(at)gmail(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pgsql-bugs<http://www.postgresql.org/mailpref/pgsql-bugs>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Wassermann | 2013-10-14 12:31:46 | Re: BUG #8461: PostgreSQL 9.3 pg_dump heap corruptions |
Previous Message | peter.reijnders | 2013-10-13 09:30:10 | BUG #8524: PQsendQueryParams with RETURNING clause on a INSERT |