Re: [ADMIN] Using pre-configured vs building Postgres

2013-01-11 Thread Armin Resch
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.3

Re: [ADMIN] Using pre-configured vs building Postgres

2013-01-09 Thread Kevin Grittner
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. htt

Re: [ADMIN] Using pre-configured vs building Postgres

2013-01-07 Thread Armin Resch
Thx, Tom. OpenSUSE's most recent postgres 9.1 is 9.1.6. Yet, 9.1.1 is what was part of the opensuse12.1 snapshot of RPMs on top of which some of our engineers develop proprietary apps. It worked well for them to freeze an RPM repo because it can happen (and did happen!) that upgrading an individual

Re: [ADMIN] Using pre-configured vs building Postgres

2013-01-07 Thread Tom Lane
Armin Resch writes: > Yet, now, we switch to a more modern distro (OpenSuse 12.1), which does > have the RPM for Perl 5.14.2 pre-installed with the option to install more > RPMs such as > perl-DBI-1.616-7.1.3 > perl-DBD-Pg-2.18.0-3.1.4 > postgresql-9.1.1-3.1.4 > Once our custom applications are