Re: Prepared statements fail after schema changes with surprising error - Mailing list pgsql-hackers

From Dickson S. Guedes
Subject Re: Prepared statements fail after schema changes with surprising error
Date
Msg-id CAHHcreoLBrcX7we3fpivrMXACHHry=naK3ptHy_P2D6c3OfbRg@mail.gmail.com
Whole thread Raw
In response to Prepared statements fail after schema changes with surprising error  (Peter van Hardenberg <pvh@pvh.ca>)
List pgsql-hackers
2013/1/21 Peter van Hardenberg <pvh@pvh.ca>:
> A user reported an interesting issue today. After restoring a dump created
> with --clean on a running application in his development environment his
> application started complaining of missing tables despite those tables very
> clearly existing.
>
> After a little thinking, we determined that this was due to the now-default
> behaviour of Rails to create prepared statements for most queries. The
> prepared statements error out because the old relation they point to is
> missing, but this gives a misleading report thus:
>
> PG::Error: ERROR: relation "xxx" does not exist

Isn't that something with search_path?

-- 
Dickson S. Guedes
mail/xmpp: guedes@guedesoft.net - skype: guediz
http://github.com/guedes - http://guedesoft.net
http://www.postgresql.org.br



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Request for vote to move forward with recovery.conf overhaul
Next
From: Robert Haas
Date:
Subject: Re: CF3+4 (was Re: Parallel query execution)