Обсуждение: PG_update to 9.0.4 in ubuntu lucid 64

Hi guys

I am getting the following:

postgres@newcollab:/usr/lib/postgresql/9.0/bin$ ./pg_upgrade -b /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/ -d /var/lib/postgresql/8.4/main -D /var/lib/postgresql/9.0/main
sh: /usr/lib/postgresql/9.0/bin/pg_config: not found
Performing Consistency Checks
-----------------------------
Checking old data directory (/var/lib/postgresql/8.4/main)  ok
Checking old bin directory (/usr/lib/postgresql/8.4/bin)    ok
Checking new data directory (/var/lib/postgresql/9.0/main)  ok
Checking new bin directory (/usr/lib/postgresql/9.0/bin)
check for pg_config failed - No such file or directory

#locate pg_config
/usr/share/locale-langpack/en_GB/LC_MESSAGES/pg_config-8.4.mo
/usr/share/postgresql-common/t/140_pg_config.t

errrm, what? what is it looking for?

Thanks

Bernhard

---

did you installed the postgresql-9.0 contrib modules?

Am Dienstag, den 22.02.2011, 14:05 +0000 schrieb Bernhard Rohrer:
> Hi guys
>
> I am getting the following:
>
> postgres@newcollab:/usr/lib/postgresql/9.0/bin$ ./pg_upgrade
> -b /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/
> -d /var/lib/postgresql/8.4/main -D /var/lib/postgresql/9.0/main
> sh: /usr/lib/postgresql/9.0/bin/pg_config: not found
> Performing Consistency Checks
> -----------------------------
> Checking old data directory (/var/lib/postgresql/8.4/main)  ok
> Checking old bin directory (/usr/lib/postgresql/8.4/bin)    ok
> Checking new data directory (/var/lib/postgresql/9.0/main)  ok
> Checking new bin directory (/usr/lib/postgresql/9.0/bin)
> check for pg_config failed - No such file or directory
>
> #locate pg_config
> /usr/share/locale-langpack/en_GB/LC_MESSAGES/pg_config-8.4.mo
> /usr/share/postgresql-common/t/140_pg_config.t
>
> errrm, what? what is it looking for?
>
> Thanks
>
> Bernhard
>
> ______________________________________________________________________
>

according to aptitude contrib is installed. But PGAdmin is also
complaining about missing modules. could it be that some stuff is
missing in Ubuntu?

Version BTW is 9.0.3-1

On 22/02/11 17:07, Bernhard Schrader wrote:
> did you installed the postgresql-9.0 contrib modules?
>
> Am Dienstag, den 22.02.2011, 14:05 +0000 schrieb Bernhard Rohrer:
>> Hi guys
>>
>> I am getting the following:
>>
>> postgres@newcollab:/usr/lib/postgresql/9.0/bin$ ./pg_upgrade
>> -b /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/
>> -d /var/lib/postgresql/8.4/main -D /var/lib/postgresql/9.0/main
>> sh: /usr/lib/postgresql/9.0/bin/pg_config: not found
>> Performing Consistency Checks
>> -----------------------------
>> Checking old data directory (/var/lib/postgresql/8.4/main)  ok
>> Checking old bin directory (/usr/lib/postgresql/8.4/bin)    ok
>> Checking new data directory (/var/lib/postgresql/9.0/main)  ok
>> Checking new bin directory (/usr/lib/postgresql/9.0/bin)
>> check for pg_config failed - No such file or directory
>>
>> #locate pg_config
>> /usr/share/locale-langpack/en_GB/LC_MESSAGES/pg_config-8.4.mo
>> /usr/share/postgresql-common/t/140_pg_config.t
>>
>> errrm, what? what is it looking for?
>>
>> Thanks
>>
>> Bernhard
>>
>> ______________________________________________________________________
>>
>
>

it was missing in my installations too, let me check what i installed..

its for debian:
libpq5, libpq-dev, libpq5/lenny-backports-sloppy,
postgresql-client-common/lenny-backports,
postgresql-common/lenny-backports,
libpq-dev/lenny-backports-sloppy,
postgresql-9.0 postgresql postgresql-contrib-9.0 postgresql-client-9.0
postgresql-server-dev-9.0


it's a little bit overkill, but there were so many dependencies if you
want to upgrade correctly. the lenny-backports-sloppy packets are the
newest packets you can get i think. don't know your repo. maybe it
helped you.
and yes, the order in which i installed all this packet is like above.
it was really necessary this way :D

greetz
Bernhard

Am Dienstag, den 22.02.2011, 18:41 +0000 schrieb Bernhard Rohrer:
> according to aptitude contrib is installed. But PGAdmin is also
> complaining about missing modules. could it be that some stuff is
> missing in Ubuntu?
>
> Version BTW is 9.0.3-1
>
> On 22/02/11 17:07, Bernhard Schrader wrote:
> > did you installed the postgresql-9.0 contrib modules?
> >
> > Am Dienstag, den 22.02.2011, 14:05 +0000 schrieb Bernhard Rohrer:
> >> Hi guys
> >>
> >> I am getting the following:
> >>
> >> postgres@newcollab:/usr/lib/postgresql/9.0/bin$ ./pg_upgrade
> >> -b /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/
> >> -d /var/lib/postgresql/8.4/main -D /var/lib/postgresql/9.0/main
> >> sh: /usr/lib/postgresql/9.0/bin/pg_config: not found
> >> Performing Consistency Checks
> >> -----------------------------
> >> Checking old data directory (/var/lib/postgresql/8.4/main)  ok
> >> Checking old bin directory (/usr/lib/postgresql/8.4/bin)    ok
> >> Checking new data directory (/var/lib/postgresql/9.0/main)  ok
> >> Checking new bin directory (/usr/lib/postgresql/9.0/bin)
> >> check for pg_config failed - No such file or directory
> >>
> >> #locate pg_config
> >> /usr/share/locale-langpack/en_GB/LC_MESSAGES/pg_config-8.4.mo
> >> /usr/share/postgresql-common/t/140_pg_config.t
> >>
> >> errrm, what? what is it looking for?
> >>
> >> Thanks
> >>
> >> Bernhard
> >>
> >> ______________________________________________________________________
> >>
> >
> >
>
>

 and here is the answer: http://ubuntuforums.org/showthread.php?t=1341411

libpq-dev is what is needed

----------------original message-----------------
From: "Bernhard Schrader" bernhard.schrader@innogames.de
To: "Bernhard Rohrer" graylion@sm-wg.net
CC: pgsql-admin@postgresql.org
Date: Tue, 22 Feb 2011 19:52:19 +0100
-------------------------------------------------


> it was missing in my installations too, let me check what i installed..
>
> its for debian:
> libpq5, libpq-dev, libpq5/lenny-backports-sloppy,
> postgresql-client-common/lenny-backports,
> postgresql-common/lenny-backports,
> libpq-dev/lenny-backports-sloppy,
> postgresql-9.0 postgresql postgresql-contrib-9.0 postgresql-client-9.0
> postgresql-server-dev-9.0
>
>
> it's a little bit overkill, but there were so many dependencies if you
> want to upgrade correctly. the lenny-backports-sloppy packets are the
> newest packets you can get i think. don't know your repo. maybe it
> helped you.
> and yes, the order in which i installed all this packet is like above.
> it was really necessary this way :D
>
> greetz
> Bernhard
>
> Am Dienstag, den 22.02.2011, 18:41 +0000 schrieb Bernhard Rohrer:
>> according to aptitude contrib is installed. But PGAdmin is also
>> complaining about missing modules. could it be that some stuff is
>> missing in Ubuntu?
>>
>> Version BTW is 9.0.3-1
>>
>> On 22/02/11 17:07, Bernhard Schrader wrote:
>> > did you installed the postgresql-9.0 contrib modules?
>> >
>> > Am Dienstag, den 22.02.2011, 14:05 +0000 schrieb Bernhard Rohrer:
>> >> Hi guys
>> >>
>> >> I am getting the following:
>> >>
>> >> postgres@newcollab :/usr/lib/postgresql/9.0/bin$ ./pg_upgrade
>> >> -b /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/
>> >> -d /var/lib/postgresql/8.4/main -D /var/lib/postgresql/9.0/main
>> >> sh: /usr/lib/postgresql/9.0/bin/pg_config: not found
>> >> Performing Consistency Checks
>> >> -----------------------------
>> >> Checking old data directory (/var/lib/postgresql/8.4/main) ok
>> >> Checking old bin directory (/usr/lib/postgresql/8.4/bin) ok
>> >> Checking new data directory (/var/lib/postgresql/9.0/main) ok
>> >> Checking new bin directory (/usr/lib/postgresql/9.0/bin)
>> >> check for pg_config failed - No such file or directory
>> >>
>> >> #locate pg_config
>> >> /usr/share/locale-langpack/en_GB/LC_MESSAGES/pg_config-8.4.mo
>> >> /usr/share/postgresql-common/t/140_pg_config.t
>> >>
>> >> errrm, what? what is it looking for?
>> >>
>> >> Thanks
>> >>
>> >> Bernhard
>> >>
>> >>
>> __________________________________________________________________
>> ____
>> >>
>> >
>> >
>>
>>
>
>
>
>
>

--
-------------
Bernhard Rohrer Consulting
529 Howth Road
Dublin 5, Ireland

+353 87 7907 134

oh and since pg_config end up in /usr/bin one also needs to symlink it to /usr/lib/postgresql/9.0/bin/

but: this leads to the next problem:

postgres@newcollab :/home/adminlion$ cd /usr/lib/postgresql/9.0/bin/ postgres@newcollab :/usr/lib/postgresql/9.0/bin$
./pg_upgrade-b /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/ -d /var/lib/postgresql/8.4/main -D
/var/lib/postgresql/9.0/main
Performing Consistency Checks
-----------------------------
Checking old data directory (/var/lib/postgresql/8.4/main) ok
Checking old bin directory (/usr/lib/postgresql/8.4/bin) ok
Checking new data directory (/var/lib/postgresql/9.0/main) ok
Checking new bin directory (/usr/lib/postgresql/9.0/bin) ok
Trying to start old server .................ok

 Unable to start old postmaster with the command: "/usr/lib/postgresql/8.4/bin/pg_ctl" -l "/dev/null" -D
"/var/lib/postgresql/8.4/main"-o "-p 5432 -c autovacuum=off -c autovacuum_freeze_max_age=2000000000" start >>
"/dev/null"2>&1 
Perhaps pg_hba.conf was not set to "trust".postgres@newcollab :/usr/lib/postgresql/9.0/bin$ exit

both pg_bha have this:

# Database administrative login by UNIX sockets
local all postgres trust #ident

# TYPE DATABASE USER CIDR-ADDRESS METHOD
host egroupware egroupware 127.0.0.1/32 password
# "local" is for Unix domain socket connections only
local all all ident
# IPv4 local connections:
host all all 127.0.0.1/32 trust #md5
host all all 172.16.0.0/21 md5
# IPv6 local connections:
host all all ::1/128 md5

any idea?

----------------original message-----------------
From: "Bernhard Rohrer" graylion@sm-wg.net
To: "Bernhard Schrader" bernhard.schrader@innogames.de
CC: pgsql-admin@postgresql.org
Date: Wed, 23 Feb 2011 08:12:19 +0000
-------------------------------------------------


> and here is the answer: http://ubuntuforums.org/showthread.php?t=1341411
>
> libpq-dev is what is needed
>
> ----------------original message-----------------
> From: "Bernhard Schrader" bernhard.schrader@innogames.de
> To: "Bernhard Rohrer" graylion@sm-wg.net
> CC: pgsql-admin@postgresql.org
> Date: Tue, 22 Feb 2011 19:52:19 +0100
> -------------------------------------------------
>
>
>> it was missing in my installations too, let me check what i installed..
>>
>> its for debian:
>> libpq5, libpq-dev, libpq5/lenny-backports-sloppy,
>> postgresql-client-common/lenny-backports,
>> postgresql-common/lenny-backports,
>> libpq-dev/lenny-backports-sloppy,
>> postgresql-9.0 postgresql postgresql-contrib-9.0
>> postgresql-client-9.0
>> postgresql-server-dev-9.0
>>
>>
>> it's a little bit overkill, but there were so many dependencies if you
>> want to upgrade correctly. the lenny-backports-sloppy packets are the
>> newest packets you can get i think. don't know your repo. maybe it
>> helped you.
>> and yes, the order in which i installed all this packet is like above.
>> it was really necessary this way :D
>>
>> greetz
>> Bernhard
>>
>> Am Dienstag, den 22.02.2011, 18:41 +0000 schrieb Bernhard Rohrer:
>>> according to aptitude contrib is installed. But PGAdmin is also
>>> complaining about missing modules. could it be that some stuff is
>>> missing in Ubuntu?
>>>
>>> Version BTW is 9.0.3-1
>>>
>>> On 22/02/11 17:07, Bernhard Schrader wrote:
>>> > did you installed the postgresql-9.0 contrib modules?
>>> >
>>> > Am Dienstag, den 22.02.2011, 14:05 +0000 schrieb Bernhard Rohrer:
>>> >> Hi guys
>>> >>
>>> >> I am getting the following:
>>> >>
>>> >> postgres@newcollab :/usr/lib/postgresql/9.0/bin$ ./pg_upgrade
>>> >> -b /usr/lib/postgresql/8.4/bin/ -B
>>> /usr/lib/postgresql/9.0/bin/
>>> >> -d /var/lib/postgresql/8.4/main -D
>>> /var/lib/postgresql/9.0/main
>>> >> sh: /usr/lib/postgresql/9.0/bin/pg_config: not found
>>> >> Performing Consistency Checks
>>> >> -----------------------------
>>> >> Checking old data directory (/var/lib/postgresql/8.4/main) ok
>>> >> Checking old bin directory (/usr/lib/postgresql/8.4/bin) ok
>>> >> Checking new data directory (/var/lib/postgresql/9.0/main) ok
>>> >> Checking new bin directory (/usr/lib/postgresql/9.0/bin)
>>> >> check for pg_config failed - No such file or directory
>>> >>
>>> >> #locate pg_config
>>> >>
>>> /usr/share/locale-langpack/en_GB/LC_MESSAGES/pg_config-8.4.mo
>>> >> /usr/share/postgresql-common/t/140_pg_config.t
>>> >>
>>> >> errrm, what? what is it looking for?
>>> >>
>>> >> Thanks
>>> >>
>>> >> Bernhard
>>> >>
>>> >>
>>>
>>> ________________________________________________________________
>>> __
>>> ____
>>> >>
>>> >
>>> >
>>>
>>>
>>
>>
>>
>>
>>
>
> --
> -------------
> Bernhard Rohrer Consulting
> 529 Howth Road
> Dublin 5, Ireland
>
> +353 87 7907 134
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org )
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

--

try to link both postgresql.conf to
your /var/lib/postgresql/8.3/main/postgresql.conf and 9.0/main


Am Mittwoch, den 23.02.2011, 08:50 +0000 schrieb Bernhard Rohrer:
> oh and since pg_config end up in /usr/bin one also needs to symlink it to /usr/lib/postgresql/9.0/bin/
>
> but: this leads to the next problem:
>
> postgres@newcollab :/home/adminlion$ cd /usr/lib/postgresql/9.0/bin/ postgres@newcollab :/usr/lib/postgresql/9.0/bin$
./pg_upgrade-b /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/ -d /var/lib/postgresql/8.4/main -D
/var/lib/postgresql/9.0/main
> Performing Consistency Checks
> -----------------------------
> Checking old data directory (/var/lib/postgresql/8.4/main) ok
> Checking old bin directory (/usr/lib/postgresql/8.4/bin) ok
> Checking new data directory (/var/lib/postgresql/9.0/main) ok
> Checking new bin directory (/usr/lib/postgresql/9.0/bin) ok
> Trying to start old server .................ok
>
>  Unable to start old postmaster with the command: "/usr/lib/postgresql/8.4/bin/pg_ctl" -l "/dev/null" -D
"/var/lib/postgresql/8.4/main"-o "-p 5432 -c autovacuum=off -c autovacuum_freeze_max_age=2000000000" start >>
"/dev/null"2>&1 
> Perhaps pg_hba.conf was not set to "trust".postgres@newcollab :/usr/lib/postgresql/9.0/bin$ exit
>
> both pg_bha have this:
>
> # Database administrative login by UNIX sockets
> local all postgres trust #ident
>
> # TYPE DATABASE USER CIDR-ADDRESS METHOD
> host egroupware egroupware 127.0.0.1/32 password
> # "local" is for Unix domain socket connections only
> local all all ident
> # IPv4 local connections:
> host all all 127.0.0.1/32 trust #md5
> host all all 172.16.0.0/21 md5
> # IPv6 local connections:
> host all all ::1/128 md5
>
> any idea?
>
> ----------------original message-----------------
> From: "Bernhard Rohrer" graylion@sm-wg.net
> To: "Bernhard Schrader" bernhard.schrader@innogames.de
> CC: pgsql-admin@postgresql.org
> Date: Wed, 23 Feb 2011 08:12:19 +0000
> -------------------------------------------------
>
>
> > and here is the answer: http://ubuntuforums.org/showthread.php?t=1341411
> >
> > libpq-dev is what is needed
> >
> > ----------------original message-----------------
> > From: "Bernhard Schrader" bernhard.schrader@innogames.de
> > To: "Bernhard Rohrer" graylion@sm-wg.net
> > CC: pgsql-admin@postgresql.org
> > Date: Tue, 22 Feb 2011 19:52:19 +0100
> > -------------------------------------------------
> >
> >
> >> it was missing in my installations too, let me check what i installed..
> >>
> >> its for debian:
> >> libpq5, libpq-dev, libpq5/lenny-backports-sloppy,
> >> postgresql-client-common/lenny-backports,
> >> postgresql-common/lenny-backports,
> >> libpq-dev/lenny-backports-sloppy,
> >> postgresql-9.0 postgresql postgresql-contrib-9.0
> >> postgresql-client-9.0
> >> postgresql-server-dev-9.0
> >>
> >>
> >> it's a little bit overkill, but there were so many dependencies if you
> >> want to upgrade correctly. the lenny-backports-sloppy packets are the
> >> newest packets you can get i think. don't know your repo. maybe it
> >> helped you.
> >> and yes, the order in which i installed all this packet is like above.
> >> it was really necessary this way :D
> >>
> >> greetz
> >> Bernhard
> >>
> >> Am Dienstag, den 22.02.2011, 18:41 +0000 schrieb Bernhard Rohrer:
> >>> according to aptitude contrib is installed. But PGAdmin is also
> >>> complaining about missing modules. could it be that some stuff is
> >>> missing in Ubuntu?
> >>>
> >>> Version BTW is 9.0.3-1
> >>>
> >>> On 22/02/11 17:07, Bernhard Schrader wrote:
> >>> > did you installed the postgresql-9.0 contrib modules?
> >>> >
> >>> > Am Dienstag, den 22.02.2011, 14:05 +0000 schrieb Bernhard Rohrer:
> >>> >> Hi guys
> >>> >>
> >>> >> I am getting the following:
> >>> >>
> >>> >> postgres@newcollab :/usr/lib/postgresql/9.0/bin$ ./pg_upgrade
> >>> >> -b /usr/lib/postgresql/8.4/bin/ -B
> >>> /usr/lib/postgresql/9.0/bin/
> >>> >> -d /var/lib/postgresql/8.4/main -D
> >>> /var/lib/postgresql/9.0/main
> >>> >> sh: /usr/lib/postgresql/9.0/bin/pg_config: not found
> >>> >> Performing Consistency Checks
> >>> >> -----------------------------
> >>> >> Checking old data directory (/var/lib/postgresql/8.4/main) ok
> >>> >> Checking old bin directory (/usr/lib/postgresql/8.4/bin) ok
> >>> >> Checking new data directory (/var/lib/postgresql/9.0/main) ok
> >>> >> Checking new bin directory (/usr/lib/postgresql/9.0/bin)
> >>> >> check for pg_config failed - No such file or directory
> >>> >>
> >>> >> #locate pg_config
> >>> >>
> >>> /usr/share/locale-langpack/en_GB/LC_MESSAGES/pg_config-8.4.mo
> >>> >> /usr/share/postgresql-common/t/140_pg_config.t
> >>> >>
> >>> >> errrm, what? what is it looking for?
> >>> >>
> >>> >> Thanks
> >>> >>
> >>> >> Bernhard
> >>> >>
> >>> >>
> >>>
> >>> ________________________________________________________________
> >>> __
> >>> ____
> >>> >>
> >>> >
> >>> >
> >>>
> >>>
> >>
> >>
> >>
> >>
> >>
> >
> > --
> > -------------
> > Bernhard Rohrer Consulting
> > 529 Howth Road
> > Dublin 5, Ireland
> >
> > +353 87 7907 134
> >
> >
> > --
> > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org )
> > To make changes to your subscription:
> > http://www.postgresql.org/mailpref/pgsql-admin
> >
>
> --
>
>
>
>
>

Thanks that worked. :)

After this and some more entertainment we are now here:

Restoring database schema to new cluster psql:/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql:24606: ERROR: column
"name"in child table must be marked NOT NULL 


There were problems executing "/usr/lib/postgresql/9.0/bin/psql" --set ON_ERROR_STOP=on --no-psqlrc --port 5432
--username"postgres" -f "/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql" --dbname template1 >> "/dev/null" 


does that mean line24606? it looks like manual edititng required ...

Thanks

Bernhard

----------------original message-----------------
From: "Bernhard Schrader" bernhard.schrader@innogames.de
To: "Bernhard Rohrer" graylion@sm-wg.net
CC: pgsql-admin@postgresql.org
Date: Wed, 23 Feb 2011 10:11:55 +0100
-------------------------------------------------


> try to link both postgresql.conf to
> your /var/lib/postgresql/8.3/main/postgresql.conf and 9.0/main
>
>
> Am Mittwoch, den 23.02.2011, 08:50 +0000 schrieb Bernhard Rohrer:
>> oh and since pg_config end up in /usr/bin one also needs to symlink it to
>> /usr/lib/postgresql/9.0/bin/
>>
>> but: this leads to the next problem:
>>
>> postgres@newcollab :/home/adminlion$ cd /usr/lib/postgresql/9.0/bin/
>> postgres@newcollab :/usr/lib/postgresql/9.0/bin$ ./pg_upgrade -b
>> /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/ -d
>> /var/lib/postgresql/8.4/main -D /var/lib/postgresql/9.0/main
>> Performing Consistency Checks
>> -----------------------------
>> Checking old data directory (/var/lib/postgresql/8.4/main) ok
>> Checking old bin directory (/usr/lib/postgresql/8.4/bin) ok
>> Checking new data directory (/var/lib/postgresql/9.0/main) ok
>> Checking new bin directory (/usr/lib/postgresql/9.0/bin) ok
>> Trying to start old server .................ok
>>
>> Unable to start old postmaster with the command:
>> "/usr/lib/postgresql/8.4/bin/pg_ctl" -l "/dev/null" -D
>> "/var/lib/postgresql/8.4/main" -o "-p 5432 -c autovacuum=off -c
>> autovacuum_freeze_max_age=2000000000" start >> "/dev/null" 2>&1
>> Perhaps pg_hba.conf was not set to "trust".postgres@newcollab
>> :/usr/lib/postgresql/9.0/bin$ exit
>>
>> both pg_bha have this:
>>
>> # Database administrative login by UNIX sockets
>> local all postgres trust #ident
>>
>> # TYPE DATABASE USER CIDR-ADDRESS METHOD
>> host egroupware egroupware 127.0.0.1/32 password
>> # "local" is for Unix domain socket connections only
>> local all all ident
>> # IPv4 local connections:
>> host all all 127.0.0.1/32 trust #md5
>> host all all 172.16.0.0/21 md5
>> # IPv6 local connections:
>> host all all ::1/128 md5
>>
>> any idea?
>>
>> ----------------original message-----------------
>> From: "Bernhard Rohrer" graylion@sm-wg.net
>> To: "Bernhard Schrader" bernhard.schrader@innogames.de
>> CC: pgsql-admin@postgresql.org
>> Date: Wed, 23 Feb 2011 08:12:19 +0000
>> -------------------------------------------------
>>
>>
>> > and here is the answer:
>> http://ubuntuforums.org/showthread.php?t=1341411
>> >
>> > libpq-dev is what is needed
>> >
>> > ----------------original message-----------------
>> > From: "Bernhard Schrader" bernhard.schrader@innogames.de
>> > To: "Bernhard Rohrer" graylion@sm-wg.net
>> > CC: pgsql-admin@postgresql.org
>> > Date: Tue, 22 Feb 2011 19:52:19 +0100
>> > -------------------------------------------------
>> >
>> >
>> >> it was missing in my installations too, let me check what i installed..
>> >>
>> >> its for debian:
>> >> libpq5, libpq-dev, libpq5/lenny-backports-sloppy,
>> >> postgresql-client-common/lenny-backports,
>> >> postgresql-common/lenny-backports,
>> >> libpq-dev/lenny-backports-sloppy,
>> >> postgresql-9.0 postgresql postgresql-contrib-9.0
>> >> postgresql-client-9.0
>> >> postgresql-server-dev-9.0
>> >>
>> >>
>> >> it's a little bit overkill, but there were so many dependencies if you
>> >> want to upgrade correctly. the lenny-backports-sloppy packets are the
>> >> newest packets you can get i think. don't know your repo. maybe it
>> >> helped you.
>> >> and yes, the order in which i installed all this packet is like above.
>> >> it was really necessary this way :D
>> >>
>> >> greetz
>> >> Bernhard
>> >>
>> >> Am Dienstag, den 22.02.2011, 18:41 +0000 schrieb Bernhard Rohrer:
>> >>> according to aptitude contrib is installed. But PGAdmin is also
>> >>> complaining about missing modules. could it be that some stuff is
>> >>> missing in Ubuntu?
>> >>>
>> >>> Version BTW is 9.0.3-1
>> >>>
>> >>> On 22/02/11 17:07, Bernhard Schrader wrote:
>> >>> > did you installed the postgresql-9.0 contrib modules?
>> >>> >
>> >>> > Am Dienstag, den 22.02.2011, 14:05 +0000 schrieb Bernhard Rohrer:
>> >>> >> Hi guys
>> >>> >>
>> >>> >> I am getting the following:
>> >>> >>
>> >>> >> postgres@newcollab :/usr/lib/postgresql/9.0/bin$ ./pg_upgrade
>> >>> >> -b /usr/lib/postgresql/8.4/bin/ -B
>> >>> /usr/lib/postgresql/9.0/bin/
>> >>> >> -d /var/lib/postgresql/8.4/main -D
>> >>> /var/lib/postgresql/9.0/main
>> >>> >> sh: /usr/lib/postgresql/9.0/bin/pg_config: not found
>> >>> >> Performing Consistency Checks
>> >>> >> -----------------------------
>> >>> >> Checking old data directory (/var/lib/postgresql/8.4/main) ok
>> >>> >> Checking old bin directory (/usr/lib/postgresql/8.4/bin) ok
>> >>> >> Checking new data directory (/var/lib/postgresql/9.0/main) ok
>> >>> >> Checking new bin directory (/usr/lib/postgresql/9.0/bin)
>> >>> >> check for pg_config failed - No such file or directory
>> >>> >>
>> >>> >> #locate pg_config
>> >>> >>
>> >>> /usr/share/locale-langpack/en_GB/LC_MESSAGES/pg_config-8.4.mo
>> >>> >> /usr/share/postgresql-common/t/140_pg_config.t
>> >>> >>
>> >>> >> errrm, what? what is it looking for?
>> >>> >>
>> >>> >> Thanks
>> >>> >>
>> >>> >> Bernhard
>> >>> >>
>> >>> >>
>> >>>
>> >>>
>> ________________________________________________________________
>> >>> __
>> >>> ____
>> >>> >>
>> >>> >
>> >>> >
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> > --
>> > -------------
>> > Bernhard Rohrer Consulting
>> > 529 Howth Road
>> > Dublin 5, Ireland
>> >
>> > +353 87 7907 134
>> >
>> >
>> > --
>> > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org )
>> > To make changes to your subscription:
>> > http://www.postgresql.org/mailpref/pgsql-admin
>> >
>>
>> --
>>
>>
>>
>>
>>
>
>

--

Bernhard Rohrer wrote:
>  Thanks that worked. :)
>
> After this and some more entertainment we are now here:
>
> Restoring database schema to new cluster
> psql:/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql:24606: ERROR:
> column "name" in child table must be marked NOT NULL
>
>
> There were problems executing "/usr/lib/postgresql/9.0/bin/psql" --set
> ON_ERROR_STOP=on --no-psqlrc --port 5432 --username "postgres" -f
> "/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql" --dbname template1
> >> "/dev/null"
>
>
> does that mean line24606? it looks like manual edititng required ...

I checked the source code and the check it is failing on has this comment:

/*
 * Check columns in child table match up with columns in parent, and increment
 * their attinhcount.
 *
 * Called by ATExecAddInherit
 *
 * Currently all parent columns must be found in child. Missing columns are an
 * error.  One day we might consider creating new columns like CREATE TABLE
 * does.  However, that is widely unpopular --- in the common use case of
 * partitioned tables it's a foot-gun.
 *
 * The data type must match exactly. If the parent column is NOT NULL then
 * the child must be as well. Defaults are not compared, however.
 */
 MergeAttributesIntoExisting()

It seems somehow your schema is corrupt --- it is pg_dump that is
failing, and threfore pg_upgrade.  We need to find out how you got into
that state.  Do a manual pg_dump and see what table is being referenced
on line 24606.  It is saying that that table has a 'name' column that is
not marked NOT NULL, while the parent table does have a NOT NULL
specification.  Those should match.  I don't remember hearing about a
bug in that area of the code.

---------------------------------------------------------------------------


>
> Thanks
>
> Bernhard
>
> ----------------original message----------------- From: "Bernhard
> Schrader" bernhard.schrader@innogames.de To: "Bernhard Rohrer"
> graylion@sm-wg.net CC: pgsql-admin@postgresql.org Date: Wed, 23 Feb
> 2011 10:11:55 +0100 -------------------------------------------------
>
>
> > try to link both postgresql.conf to
> > your /var/lib/postgresql/8.3/main/postgresql.conf and 9.0/main
> >
> >
> > Am Mittwoch, den 23.02.2011, 08:50 +0000 schrieb Bernhard Rohrer:
> >> oh and since pg_config end up in /usr/bin one also needs to symlink it to
> >> /usr/lib/postgresql/9.0/bin/
> >>
> >> but: this leads to the next problem:
> >>
> >> postgres@newcollab :/home/adminlion$ cd /usr/lib/postgresql/9.0/bin/
> >> postgres@newcollab :/usr/lib/postgresql/9.0/bin$ ./pg_upgrade -b
> >> /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/ -d
> >> /var/lib/postgresql/8.4/main -D /var/lib/postgresql/9.0/main
> >> Performing Consistency Checks
> >> -----------------------------
> >> Checking old data directory (/var/lib/postgresql/8.4/main) ok
> >> Checking old bin directory (/usr/lib/postgresql/8.4/bin) ok
> >> Checking new data directory (/var/lib/postgresql/9.0/main) ok
> >> Checking new bin directory (/usr/lib/postgresql/9.0/bin) ok
> >> Trying to start old server .................ok
> >>
> >> Unable to start old postmaster with the command:
> >> "/usr/lib/postgresql/8.4/bin/pg_ctl" -l "/dev/null" -D
> >> "/var/lib/postgresql/8.4/main" -o "-p 5432 -c autovacuum=off -c
> >> autovacuum_freeze_max_age=2000000000" start >> "/dev/null" 2>&1
> >> Perhaps pg_hba.conf was not set to "trust".postgres@newcollab
> >> :/usr/lib/postgresql/9.0/bin$ exit
> >>
> >> both pg_bha have this:
> >>
> >> # Database administrative login by UNIX sockets
> >> local all postgres trust #ident
> >>
> >> # TYPE DATABASE USER CIDR-ADDRESS METHOD
> >> host egroupware egroupware 127.0.0.1/32 password
> >> # "local" is for Unix domain socket connections only
> >> local all all ident
> >> # IPv4 local connections:
> >> host all all 127.0.0.1/32 trust #md5
> >> host all all 172.16.0.0/21 md5
> >> # IPv6 local connections:
> >> host all all ::1/128 md5
> >>
> >> any idea?
> >>
> >> ----------------original message-----------------
> >> From: "Bernhard Rohrer" graylion@sm-wg.net
> >> To: "Bernhard Schrader" bernhard.schrader@innogames.de
> >> CC: pgsql-admin@postgresql.org
> >> Date: Wed, 23 Feb 2011 08:12:19 +0000
> >> -------------------------------------------------
> >>
> >>
> >> > and here is the answer:
> >> http://ubuntuforums.org/showthread.php?t=1341411
> >> >
> >> > libpq-dev is what is needed
> >> >
> >> > ----------------original message-----------------
> >> > From: "Bernhard Schrader" bernhard.schrader@innogames.de
> >> > To: "Bernhard Rohrer" graylion@sm-wg.net
> >> > CC: pgsql-admin@postgresql.org
> >> > Date: Tue, 22 Feb 2011 19:52:19 +0100
> >> > -------------------------------------------------
> >> >
> >> >
> >> >> it was missing in my installations too, let me check what i installed..
> >> >>
> >> >> its for debian:
> >> >> libpq5, libpq-dev, libpq5/lenny-backports-sloppy,
> >> >> postgresql-client-common/lenny-backports,
> >> >> postgresql-common/lenny-backports,
> >> >> libpq-dev/lenny-backports-sloppy,
> >> >> postgresql-9.0 postgresql postgresql-contrib-9.0
> >> >> postgresql-client-9.0
> >> >> postgresql-server-dev-9.0
> >> >>
> >> >>
> >> >> it's a little bit overkill, but there were so many dependencies if you
> >> >> want to upgrade correctly. the lenny-backports-sloppy packets are the
> >> >> newest packets you can get i think. don't know your repo. maybe it
> >> >> helped you.
> >> >> and yes, the order in which i installed all this packet is like above.
> >> >> it was really necessary this way :D
> >> >>
> >> >> greetz
> >> >> Bernhard
> >> >>
> >> >> Am Dienstag, den 22.02.2011, 18:41 +0000 schrieb Bernhard Rohrer:
> >> >>> according to aptitude contrib is installed. But PGAdmin is also
> >> >>> complaining about missing modules. could it be that some stuff is
> >> >>> missing in Ubuntu?
> >> >>>
> >> >>> Version BTW is 9.0.3-1
> >> >>>
> >> >>> On 22/02/11 17:07, Bernhard Schrader wrote:
> >> >>> > did you installed the postgresql-9.0 contrib modules?
> >> >>> >
> >> >>> > Am Dienstag, den 22.02.2011, 14:05 +0000 schrieb Bernhard Rohrer:
> >> >>> >> Hi guys
> >> >>> >>
> >> >>> >> I am getting the following:
> >> >>> >>
> >> >>> >> postgres@newcollab :/usr/lib/postgresql/9.0/bin$ ./pg_upgrade
> >> >>> >> -b /usr/lib/postgresql/8.4/bin/ -B
> >> >>> /usr/lib/postgresql/9.0/bin/
> >> >>> >> -d /var/lib/postgresql/8.4/main -D
> >> >>> /var/lib/postgresql/9.0/main
> >> >>> >> sh: /usr/lib/postgresql/9.0/bin/pg_config: not found
> >> >>> >> Performing Consistency Checks
> >> >>> >> -----------------------------
> >> >>> >> Checking old data directory (/var/lib/postgresql/8.4/main) ok
> >> >>> >> Checking old bin directory (/usr/lib/postgresql/8.4/bin) ok
> >> >>> >> Checking new data directory (/var/lib/postgresql/9.0/main) ok
> >> >>> >> Checking new bin directory (/usr/lib/postgresql/9.0/bin)
> >> >>> >> check for pg_config failed - No such file or directory
> >> >>> >>
> >> >>> >> #locate pg_config
> >> >>> >>
> >> >>> /usr/share/locale-langpack/en_GB/LC_MESSAGES/pg_config-8.4.mo
> >> >>> >> /usr/share/postgresql-common/t/140_pg_config.t
> >> >>> >>
> >> >>> >> errrm, what? what is it looking for?
> >> >>> >>
> >> >>> >> Thanks
> >> >>> >>
> >> >>> >> Bernhard
> >> >>> >>
> >> >>> >>
> >> >>>
> >> >>>
> >> ________________________________________________________________
> >> >>> __
> >> >>> ____
> >> >>> >>
> >> >>> >
> >> >>> >
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >> > --
> >> > -------------
> >> > Bernhard Rohrer Consulting
> >> > 529 Howth Road
> >> > Dublin 5, Ireland
> >> >
> >> > +353 87 7907 134
> >> >
> >> >
> >> > --
> >> > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org )
> >> > To make changes to your subscription:
> >> > http://www.postgresql.org/mailpref/pgsql-admin
> >> >
> >>
> >> --
> >>
> >>
> >>
> >>
> >>
> >
> >
>
> --
>
>
>
>
> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To
> make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

Bruce Momjian wrote:
> Bernhard Rohrer wrote:
> >  Thanks that worked. :)
> >
> > After this and some more entertainment we are now here:
> >
> > Restoring database schema to new cluster
> > psql:/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql:24606: ERROR:
> > column "name" in child table must be marked NOT NULL
> >
> >
> > There were problems executing "/usr/lib/postgresql/9.0/bin/psql" --set
> > ON_ERROR_STOP=on --no-psqlrc --port 5432 --username "postgres" -f
> > "/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql" --dbname template1
> > >> "/dev/null"
> >
> >
> > does that mean line24606? it looks like manual edititng required ...
>
> I checked the source code and the check it is failing on has this comment:
>
> /*
>  * Check columns in child table match up with columns in parent, and increment
>  * their attinhcount.
>  *
>  * Called by ATExecAddInherit
>  *
>  * Currently all parent columns must be found in child. Missing columns are an
>  * error.  One day we might consider creating new columns like CREATE TABLE
>  * does.  However, that is widely unpopular --- in the common use case of
>  * partitioned tables it's a foot-gun.
>  *
>  * The data type must match exactly. If the parent column is NOT NULL then
>  * the child must be as well. Defaults are not compared, however.
>  */
>  MergeAttributesIntoExisting()
>
> It seems somehow your schema is corrupt --- it is pg_dump that is
> failing, and threfore pg_upgrade.  We need to find out how you got into
> that state.  Do a manual pg_dump and see what table is being referenced
> on line 24606.  It is saying that that table has a 'name' column that is
> not marked NOT NULL, while the parent table does have a NOT NULL
> specification.  Those should match.  I don't remember hearing about a
> bug in that area of the code.

FYI, you can easily reproduce the failure by trying to restore a pg_dump
--schema dump into an empty database.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

 thanks guys

It'll be a few days before i can do that, but will come back and report. Can i use the dump file that pg_upgrade
produced?it is there after all. 

thanks

B
----------------original message-----------------
From: "Bruce Momjian"
To: "Bruce Momjian"
CC: "Bernhard Rohrer" graylion@sm-wg.net , "Bernhard Schrader" bernhard.schrader@innogames.de ,
pgsql-admin@postgresql.org 
Date: Wed, 23 Feb 2011 18:37:40 -0500 (EST)
-------------------------------------------------


> Bruce Momjian wrote:
>> Bernhard Rohrer wrote:
>> > Thanks that worked. :)
>> >
>> > After this and some more entertainment we are now here:
>> >
>> > Restoring database schema to new cluster
>> > psql:/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql:24606:
>> ERROR:
>> > column "name" in child table must be marked NOT NULL
>> >
>> >
>> > There were problems executing "/usr/lib/postgresql/9.0/bin/psql"
>> --set
>> > ON_ERROR_STOP=on --no-psqlrc --port 5432 --username "postgres" -f
>> > "/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql" --dbname
>> template1
>> > >> "/dev/null"
>> >
>> >
>> > does that mean line24606? it looks like manual edititng required ...
>>
>> I checked the source code and the check it is failing on has this comment:
>>
>> /*
>> * Check columns in child table match up with columns in parent, and increment
>> * their attinhcount.
>> *
>> * Called by ATExecAddInherit
>> *
>> * Currently all parent columns must be found in child. Missing columns are an
>> * error. One day we might consider creating new columns like CREATE TABLE
>> * does. However, that is widely unpopular --- in the common use case of
>> * partitioned tables it's a foot-gun.
>> *
>> * The data type must match exactly. If the parent column is NOT NULL then
>> * the child must be as well. Defaults are not compared, however.
>> */
>> MergeAttributesIntoExisting()
>>
>> It seems somehow your schema is corrupt --- it is pg_dump that is
>> failing, and threfore pg_upgrade. We need to find out how you got into
>> that state. Do a manual pg_dump and see what table is being referenced
>> on line 24606. It is saying that that table has a 'name' column that is
>> not marked NOT NULL, while the parent table does have a NOT NULL
>> specification. Those should match. I don't remember hearing about a
>> bug in that area of the code.
>
> FYI, you can easily reproduce the failure by trying to restore a pg_dump
> --schema dump into an empty database.
>
> --
> Bruce Momjian
 http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + It's impossible for everything to be true. +
>

--
-------------
Bernhard Rohrer Consulting
529 Howth Road
Dublin 5, Ireland

+353 87 7907 134

Bernhard Rohrer wrote:
>
>  thanks guys
>
> It'll be a few days before i can do that, but will come back and report.
> Can i use the dump file that pg_upgrade produced? it is there after
> all.

Yes, you can use the dump file pg_upgrade creates to see the table name
producing the error.  Also, a --schema-only pg_dump is a small file, or
should be.

---------------------------------------------------------------------------


>
> thanks
>
> B ----------------original message----------------- From: "Bruce
> Momjian" To: "Bruce Momjian" CC: "Bernhard Rohrer" graylion@sm-wg.net
> , "Bernhard Schrader" bernhard.schrader@innogames.de ,
> pgsql-admin@postgresql.org Date: Wed, 23 Feb 2011 18:37:40 -0500 (EST)
> -------------------------------------------------
>
>
> > Bruce Momjian wrote:
> >> Bernhard Rohrer wrote:
> >> > Thanks that worked. :)
> >> >
> >> > After this and some more entertainment we are now here:
> >> >
> >> > Restoring database schema to new cluster
> >> > psql:/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql:24606:
> >> ERROR:
> >> > column "name" in child table must be marked NOT NULL
> >> >
> >> >
> >> > There were problems executing "/usr/lib/postgresql/9.0/bin/psql"
> >> --set
> >> > ON_ERROR_STOP=on --no-psqlrc --port 5432 --username "postgres" -f
> >> > "/usr/lib/postgresql/9.0/bin/pg_upgrade_dump_db.sql" --dbname
> >> template1
> >> > >> "/dev/null"
> >> >
> >> >
> >> > does that mean line24606? it looks like manual edititng required ...
> >>
> >> I checked the source code and the check it is failing on has this comment:
> >>
> >> /*
> >> * Check columns in child table match up with columns in parent, and increment
> >> * their attinhcount.
> >> *
> >> * Called by ATExecAddInherit
> >> *
> >> * Currently all parent columns must be found in child. Missing columns are an
> >> * error. One day we might consider creating new columns like CREATE TABLE
> >> * does. However, that is widely unpopular --- in the common use case of
> >> * partitioned tables it's a foot-gun.
> >> *
> >> * The data type must match exactly. If the parent column is NOT NULL then
> >> * the child must be as well. Defaults are not compared, however.
> >> */
> >> MergeAttributesIntoExisting()
> >>
> >> It seems somehow your schema is corrupt --- it is pg_dump that is
> >> failing, and threfore pg_upgrade. We need to find out how you got into
> >> that state. Do a manual pg_dump and see what table is being referenced
> >> on line 24606. It is saying that that table has a 'name' column that is
> >> not marked NOT NULL, while the parent table does have a NOT NULL
> >> specification. Those should match. I don't remember hearing about a
> >> bug in that area of the code.
> >
> > FYI, you can easily reproduce the failure by trying to restore a pg_dump
> > --schema dump into an empty database.
> >
> > --
> > Bruce Momjian
>  http://momjian.us
> > EnterpriseDB http://enterprisedb.com
> >
> > + It's impossible for everything to be true. +
> >
>
> -- ------------- Bernhard Rohrer Consulting 529 Howth Road Dublin 5,
> Ireland
>
> +353 87 7907 134

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +