Indeed, 9.1.1 produced log entries complaining about a non-existent schema which clearly exists, and I confirmed 9.1.6 behaves.
...
2013-01-10 15:49:45.068 CST - - 50ef3779.377: WARNING: invalid value for parameter "search_path": "beverlyhills, public"
2013-01-10 15:49:45.068 CST - - 50ef3779.377: DETAIL: schema "beverlyhills" does not exist
2013-01-10 15:50:15.080 CST - - 50ef3797.394: WARNING: invalid value for parameter "search_path": "beverlyhills, public"
2013-01-10 15:50:15.080 CST - - 50ef3797.394: DETAIL: schema "beverlyhills" does not exist
2013-01-10 15:50:30.082 CST - - 50ef37a6.3a3: WARNING: invalid value for parameter "search_path": "beverlyhills, public"
2013-01-10 15:50:30.083 CST - - 50ef37a6.3a3: DETAIL: schema "beverlyhills" does not exist
2013-01-10 15:50:45.124 CST - - 50ef37b5.3b1: WARNING: invalid value for parameter "search_path": "beverlyhills, public"
2013-01-10 15:50:45.125 CST - - 50ef37b5.3b1: DETAIL: schema "beverlyhills" does not exist
...
-ar
On Wed, Jan 9, 2013 at 3:59 PM, Kevin Grittner <kgrittn@mail.com> wrote:
Armin Resch wrote:
> one needs to evaluate to what extent an upgrade of postgres is contained
PostgreSQL minor releases (where the version number matches to the left of the second dot) only contain fixes for bugs and security vulnerabilities. Dependencies on other packages should not change.