BUG #8515: Random 'relation "..." does not exist'

On 9.10.2013 19:35, nbuduroi@gmail.com wrote:

The following bug has been logged on the website:

Bug reference: 8515
Logged by: Nicolas Buduroi
Email address: nbuduroi@gmail.com
PostgreSQL version: 9.2.4
Operating system: ArchLinux
Description:

We've recently migrated an application from MySQL to Postgres and I've been
experiencing some really strange and random bugs. The application is a
pretty simple Rails application and the Postgres setup is the default one
provided by ArchLinux.

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.

This only happen on a development machine which is running version 9.2.4 of
Postgres. We've not encountered this error on our production/staging/ci
servers which are running Postgres 9.1.9 version.

Hi Nicolas,

can you check PostgreSQL logs? I'm not familiar with Arch Linux but I
guess it might be /var/log/postgresql.log or something like that.

Is there anything relevant in the logs?

Can you explain what is the application doing? Can you try to prepare a
simplified testcase, based on your knowledge of the app?

kind regards
Tomas

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On 10/9/2013 10:35 AM, nbuduroi@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

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@hogranch.com> wrote: