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

[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.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  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.
>
> http://www.postgresql.org/support/versioning/
>
> -Kevin
>

Re: [ADMIN] pg_dump and restore

[Kevin Grittner]

suhas.basavaraj12 wrote:

> We will be dumping data from version 9.0 and restore to 9.1.

That should work fine, as long as use use pg_dump from version
9.1 to dump the 9.0 database.

-Kevin


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