[gentoo-user] pg_upgrade from 9.0.5 to 9.1.1

2011-11-12 Thread Michael George
I am trying to upgrade my postgresql server from 9.0 to 9.1.  I've
installed 9.1.1 and used eselect to make it the slot to run for the
system.

When I run:
pg_upgrade -v --check -d /var/lib/postgresql/9.0/data -D \
/var/lib/postgresql/9.1/data -b /usr/lib64/postgresql-9.0/bin -B \
/usr/lib64/postgresql-9.1/bin

I get:
Running in verbose mode
Performing Consistency Checks
-
Checking current, bin, and data directories ok
Checking cluster versions   ok
/usr/lib64/postgresql-9.0/bin/pg_ctl -w -l /dev/null -D
/var/lib/postgresql/9.0/data -o -p 5432 -c autovacuum=off -c
autovacuum_freeze_max_age=20 start  /dev/null 21

When I run that command manually and send the output to a logfile, it
appears that it's trying to find postgresql's *.conf files in the data
directory rather than in /etc/postgresql-9.0.  I don't see a way to
specify the location of the conf files separate from the data files.

How do I proceed?

-- 
-Michael

Rident stolidi verba Latina.
-Ovid



Re: [gentoo-user] pg_upgrade from 9.0.5 to 9.1.1

2011-11-12 Thread Pandu Poluan
On Nov 13, 2011 12:35 PM, Michael George geo...@mutualdata.com wrote:

 I am trying to upgrade my postgresql server from 9.0 to 9.1.  I've
 installed 9.1.1 and used eselect to make it the slot to run for the
 system.

 When I run:
 pg_upgrade -v --check -d /var/lib/postgresql/9.0/data -D \
 /var/lib/postgresql/9.1/data -b /usr/lib64/postgresql-9.0/bin -B \
 /usr/lib64/postgresql-9.1/bin

 I get:
 Running in verbose mode
 Performing Consistency Checks
 -
 Checking current, bin, and data directories ok
 Checking cluster versions   ok
 /usr/lib64/postgresql-9.0/bin/pg_ctl -w -l /dev/null -D
 /var/lib/postgresql/9.0/data -o -p 5432 -c autovacuum=off -c
 autovacuum_freeze_max_age=20 start  /dev/null 21

 When I run that command manually and send the output to a logfile, it
 appears that it's trying to find postgresql's *.conf files in the data
 directory rather than in /etc/postgresql-9.0.  I don't see a way to
 specify the location of the conf files separate from the data files.

 How do I proceed?


I'm not (yet) well-versed in postgresql, but have you tried creating
symlinks?

Rgds,


Re: [gentoo-user] pg_upgrade from 9.0.5 to 9.1.1

2011-11-12 Thread Michael George
On Sun, Nov 13, 2011 at 12:31:58AM -0500, Michael George wrote:
 I am trying to upgrade my postgresql server from 9.0 to 9.1.  I've
 installed 9.1.1 and used eselect to make it the slot to run for the
 system.
 
 When I run:
 pg_upgrade -v --check -d /var/lib/postgresql/9.0/data -D \
 /var/lib/postgresql/9.1/data -b /usr/lib64/postgresql-9.0/bin -B \
 /usr/lib64/postgresql-9.1/bin
 
 I get:
 Running in verbose mode
 Performing Consistency Checks
 -
 Checking current, bin, and data directories ok
 Checking cluster versions   ok
 /usr/lib64/postgresql-9.0/bin/pg_ctl -w -l /dev/null -D
 /var/lib/postgresql/9.0/data -o -p 5432 -c autovacuum=off -c
 autovacuum_freeze_max_age=20 start  /dev/null 21
 
 When I run that command manually and send the output to a logfile, it
 appears that it's trying to find postgresql's *.conf files in the data
 directory rather than in /etc/postgresql-9.0.  I don't see a way to
 specify the location of the conf files separate from the data files.
 
 How do I proceed?

According to:
http://archives.postgresql.org/pgsql-hackers/2011-09/msg01482.php

The normal workaround is to make symlinks and delete them after the
pg_upgrade.  It appears they might implement a solution, but it isn't in
place for 9.1.  :(

-- 
-M

Rident stolidi verba Latina.
-Ovid