Thread: Problem pg_upgradecluster from 9.1 to 9.3

Hi all,

I have a problem when I try to upgrade my pgsql 9.1 cluster to 9.3

This is my output :

root@p2tstl2mondbm:/var/lib/postgresql# pg_upgradecluster 9.1 main
Disabling connections to the old cluster during upgrade...
Restarting old cluster with restricted connections...
Removed stale pid file.
Creating new cluster 9.3/main ...
   config /etc/postgresql/9.3/main
   data   /var/lib/postgresql/9.3/main
   locale C
   port   5433
Disabling connections to the new cluster during upgrade...
Error: automatic upgrade of tablespaces is not supported
Re-enabling connections to the old cluster...
Re-enabling connections to the new cluster...
Error during cluster dumping, removing new cluster


On my db I have 2 tablespaces :


postgres=# \db+
                                          List of tablespaces
      Name     |  Owner   |                Location                 |
Access privileges | Description
--------------+----------+-----------------------------------------+-------------------+-------------
  envers       | postgres | /var/lib/postgresql/tablespaces/envers
|                   |
  indexes_fast | postgres | /var/lib/postgresql/tablespaces/indexes
|                   |
  pg_default   | postgres | |                   |
  pg_global    | postgres | |                   |
(4 rows)

postgres=#

This is my path config :

postgres@p2tstl2mondbm:~$ cd /var/lib/postgresql/
postgres@p2tstl2mondbm:/var/lib/postgresql$ ls -all
total 36
drwxr-xr-x  6 postgres postgres  4096 Dec  4 12:22 .
drwxr-xr-x 27 root     root      4096 Dec  4 08:17 ..
drwxr-xr-x  4 postgres postgres  4096 Oct  7 07:42 9.1
drwxr-xr-x  2 postgres postgres  4096 Dec  5 10:58 9.3
drwx------  2 postgres postgres 16384 Mar  4  2013 lost+found
drwx------  4 postgres postgres  4096 Mar  8  2013 tablespaces
postgres@p2tstl2mondbm:/var/lib/postgresql$


My pgsql versions :

i  postgresql                             9.1+134wheezy4
all                      object-relational SQL database (supported version)
ii  postgresql-9.1                         9.1.14-0+deb7u1
amd64                    object-relational SQL database, version 9.1 server
ii  postgresql-9.3                         9.3.5-1.pgdg70+1
amd64                    object-relational SQL database, version 9.3 server


I don't find any tips on the web to help me

Thank you for your advice.

Matthieu Lejeune

Hi Matthieu,

Are you following the steps from here: http://nixmash.com/postgresql/upgrading-postgresql-9-1-to-9-3-in-ubuntu/

What's the current output of `pg_lscluster`?

-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Matthieu Lejeune
Sent: December 05, 2014 11:06 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Problem pg_upgradecluster from 9.1 to 9.3

Hi all,

I have a problem when I try to upgrade my pgsql 9.1 cluster to 9.3

This is my output :

root@p2tstl2mondbm:/var/lib/postgresql# pg_upgradecluster 9.1 main
Disabling connections to the old cluster during upgrade...
Restarting old cluster with restricted connections...
Removed stale pid file.
Creating new cluster 9.3/main ...   config /etc/postgresql/9.3/main   data   /var/lib/postgresql/9.3/main   locale C   port   5433
Disabling connections to the new cluster during upgrade...
Error: automatic upgrade of tablespaces is not supported
Re-enabling connections to the old cluster...
Re-enabling connections to the new cluster...
Error during cluster dumping, removing new cluster


On my db I have 2 tablespaces :


postgres=# \db+                                          List of tablespaces      Name     |  Owner   |                Location                 | 
Access privileges | Description
--------------+----------+-----------------------------------------+-------------------+-------------  envers       | postgres | /var/lib/postgresql/tablespaces/envers 
|                   |  indexes_fast | postgres | /var/lib/postgresql/tablespaces/indexes 
|                   |  pg_default   | postgres | |                   |  pg_global    | postgres | |                   |
(4 rows)

postgres=#

This is my path config :

postgres@p2tstl2mondbm:~$ cd /var/lib/postgresql/
postgres@p2tstl2mondbm:/var/lib/postgresql$ ls -all
total 36
drwxr-xr-x  6 postgres postgres  4096 Dec  4 12:22 .
drwxr-xr-x 27 root     root      4096 Dec  4 08:17 ..
drwxr-xr-x  4 postgres postgres  4096 Oct  7 07:42 9.1
drwxr-xr-x  2 postgres postgres  4096 Dec  5 10:58 9.3
drwx------  2 postgres postgres 16384 Mar  4  2013 lost+found
drwx------  4 postgres postgres  4096 Mar  8  2013 tablespaces
postgres@p2tstl2mondbm:/var/lib/postgresql$


My pgsql versions :

i  postgresql                             9.1+134wheezy4 
all                      object-relational SQL database (supported version)
ii  postgresql-9.1                         9.1.14-0+deb7u1 
amd64                    object-relational SQL database, version 9.1 server
ii  postgresql-9.3                         9.3.5-1.pgdg70+1 
amd64                    object-relational SQL database, version 9.3 server


I don't find any tips on the web to help me

Thank you for your advice.

Matthieu Lejeune

--

Matthieu Lejeune, System Engineer | Gsm: +32(0)491/52.70.66
Exxoss,  SPRL
Rue de la station, 2, 4347, Fexhe-le-haut-clocher | Telephone: +32(0)4/341.25.81 | Fax: +32(0)4/371.94.06

Hi Matthieu,

Are you following the steps from here: http://nixmash.com/postgresql/upgrading-postgresql-9-1-to-9-3-in-ubuntu/

What's the current output of `pg_lscluster`?

-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Matthieu Lejeune
Sent: December 05, 2014 11:06 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Problem pg_upgradecluster from 9.1 to 9.3

Hi all,

I have a problem when I try to upgrade my pgsql 9.1 cluster to 9.3

This is my output :

root@p2tstl2mondbm:/var/lib/postgresql# pg_upgradecluster 9.1 main
Disabling connections to the old cluster during upgrade...
Restarting old cluster with restricted connections...
Removed stale pid file.
Creating new cluster 9.3/main ...
   config /etc/postgresql/9.3/main
   data   /var/lib/postgresql/9.3/main
   locale C
   port   5433
Disabling connections to the new cluster during upgrade...
Error: automatic upgrade of tablespaces is not supported
Re-enabling connections to the old cluster...
Re-enabling connections to the new cluster...
Error during cluster dumping, removing new cluster


On my db I have 2 tablespaces :


postgres=# \db+
                                          List of tablespaces
      Name     |  Owner   |                Location                 | 
Access privileges | Description
--------------+----------+-----------------------------------------+-------------------+-------------
  envers       | postgres | /var/lib/postgresql/tablespaces/envers 
|                   |
  indexes_fast | postgres | /var/lib/postgresql/tablespaces/indexes 
|                   |
  pg_default   | postgres | |                   |
  pg_global    | postgres | |                   |
(4 rows)

postgres=#

This is my path config :

postgres@p2tstl2mondbm:~$ cd /var/lib/postgresql/
postgres@p2tstl2mondbm:/var/lib/postgresql$ ls -all
total 36
drwxr-xr-x  6 postgres postgres  4096 Dec  4 12:22 .
drwxr-xr-x 27 root     root      4096 Dec  4 08:17 ..
drwxr-xr-x  4 postgres postgres  4096 Oct  7 07:42 9.1
drwxr-xr-x  2 postgres postgres  4096 Dec  5 10:58 9.3
drwx------  2 postgres postgres 16384 Mar  4  2013 lost+found
drwx------  4 postgres postgres  4096 Mar  8  2013 tablespaces
postgres@p2tstl2mondbm:/var/lib/postgresql$


My pgsql versions :

i  postgresql                             9.1+134wheezy4 
all                      object-relational SQL database (supported version)
ii  postgresql-9.1                         9.1.14-0+deb7u1 
amd64                    object-relational SQL database, version 9.1 server
ii  postgresql-9.3                         9.3.5-1.pgdg70+1 
amd64                    object-relational SQL database, version 9.3 server


I don't find any tips on the web to help me

Thank you for your advice.

Matthieu Lejeune



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

On 12/5/14 5:06 AM, Matthieu Lejeune wrote:
> Error: automatic upgrade of tablespaces is not supported

This restriction appears to be outdated, because you can now upgrade
tablespaces in place.

If you are slightly daring, you can just patch the check out of the script.

Of you can use --method=upgrade, which does not contain that check.

On 12/5/14 5:06 AM, Matthieu Lejeune wrote:

Error: automatic upgrade of tablespaces is not supported

This restriction appears to be outdated, because you can now upgrade
tablespaces in place.

If you are slightly daring, you can just patch the check out of the script.

Of you can use --method=upgrade, which does not contain that check.

--

Matthieu Lejeune, System Engineer | Gsm: +32(0)491/52.70.66
Exxoss,  SPRL
Rue de la station, 2, 4347, Fexhe-le-haut-clocher | Telephone: +32(0)4/341.25.81 | Fax: +32(0)4/371.94.06

On 12/6/14 3:14 AM, Matthieu Lejeune wrote:
> Creating new cluster 9.3/main ...
>   config /etc/postgresql/9.3/main
>   data   /var/lib/postgresql/9.3/main
>   locale C
>   port   5433
> Error: could not symlink configuration file
> Error during cluster dumping, removing new cluster
> pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
> exist
> Is server running?
> Error: could not reload old cluster, please do that manually
> root@p2tstl2mondbm:/var/lib/postgresql#

It's trying to symlink the configuration files into the data directory
before calling pg_upgrade.  I think it complains that the symlinks are
already there, from a previous runs.  Could could try manually removing
them from the data directory.

This was apparently fixed in postgresql-common version 155 (see
https://github.com/petere/postgresql-common/commit/323253ed95ec00faaf042217749e3f4c7e3617b3).
 If you want to, you could also try to get an updated version from
apt.postgresql.org.

Hi,

I have upgraded the postgresql-common and postgresql-client-common :

ii  postgresql-9.1 9.1.14-1.pgdg70+1         amd64 object-relational SQL
database, version 9.1 server
ii  postgresql-9.3 9.3.5-1.pgdg70+1          amd64 object-relational SQL
database, version 9.3 server
ii  postgresql-client-9.1 9.1.14-1.pgdg70+1
amd64                     front-end programs for PostgreSQL 9.1
ii  postgresql-client-9.3 9.3.5-1.pgdg70+1
amd64                     front-end programs for PostgreSQL 9.3
ii  postgresql-client-common 163
all                       manager for multiple PostgreSQL client versions
iF  postgresql-common 163
all                       PostgreSQL database-cluster manager


But I got the same error :

root@p2tstl2mondbm:/var/lib# pg_upgradecluster 9.1 main --method=upgrade
Disabling connections to the old cluster during upgrade...
Restarting old cluster with restricted connections...
Stopping old cluster...
Creating new cluster 9.3/main ...
   config /etc/postgresql/9.3/main
   data   /var/lib/postgresql/9.3/main
   locale C
Flags of /var/lib/postgresql/9.3/main set as ---------------C
   port   5433
Error: could not create symlink /var/lib/postgresql/9.1/main/pg_ident.conf
Re-enabling connections to the old cluster...
Error during cluster dumping, removing new cluster
pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
exist
Is server running?
Error: could not reload old cluster, please do that manually
root@p2tstl2mondbm:/var/lib#

Thanks a lot for your help

Matthieu


Le 6/12/14 14:56, Peter Eisentraut a écrit :
> On 12/6/14 3:14 AM, Matthieu Lejeune wrote:
>> Creating new cluster 9.3/main ...
>>    config /etc/postgresql/9.3/main
>>    data   /var/lib/postgresql/9.3/main
>>    locale C
>>    port   5433
>> Error: could not symlink configuration file
>> Error during cluster dumping, removing new cluster
>> pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
>> exist
>> Is server running?
>> Error: could not reload old cluster, please do that manually
>> root@p2tstl2mondbm:/var/lib/postgresql#
> It's trying to symlink the configuration files into the data directory
> before calling pg_upgrade.  I think it complains that the symlinks are
> already there, from a previous runs.  Could could try manually removing
> them from the data directory.
>
> This was apparently fixed in postgresql-common version 155 (see
> https://github.com/petere/postgresql-common/commit/323253ed95ec00faaf042217749e3f4c7e3617b3).
>   If you want to, you could also try to get an updated version from
> apt.postgresql.org.
>
>
>

On 12/8/14 2:37 AM, Matthieu Lejeune wrote:
> I have upgraded the postgresql-common and postgresql-client-common :

> But I got the same error :
>
> root@p2tstl2mondbm:/var/lib# pg_upgradecluster 9.1 main --method=upgrade
> Disabling connections to the old cluster during upgrade...
> Restarting old cluster with restricted connections...
> Stopping old cluster...
> Creating new cluster 9.3/main ...
>   config /etc/postgresql/9.3/main
>   data   /var/lib/postgresql/9.3/main
>   locale C
> Flags of /var/lib/postgresql/9.3/main set as ---------------C
>   port   5433
> Error: could not create symlink /var/lib/postgresql/9.1/main/pg_ident.conf
> Re-enabling connections to the old cluster...
> Error during cluster dumping, removing new cluster
> pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
> exist
> Is server running?
> Error: could not reload old cluster, please do that manually

At this point, I think you should add some manual debug statements into
the script and see what's going on.  The script itself is not very
complicated, so you can tweak to make it work for you.

Hi,

I have try manualy with pg_upgrade but I got this error :


root@p2tstl2mondbm:/# sudo su - postgres -c
'/usr/lib/postgresql/9.3/bin/pg_upgrade \
                         -b /usr/lib/postgresql/9.1/bin \
                         -B /usr/lib/postgresql/9.3/bin \
                         -d /var/lib/postgresql/9.1/main/ \
                         -D /var/lib/postgresql/9.3/main/ \
                         -O " -c
config_file=/etc/postgresql/9.3/main/postgresql.conf" \
                         -o " -c
config_file=/etc/postgresql/9.1/main/postgresql.conf"'
Performing Consistency Checks
-----------------------------
Checking cluster versions                                   ok
Checking database user is a superuser                       ok
Checking for prepared transactions                          ok
Checking for reg* system OID user data types                ok
Checking for contrib/isn with bigint-passing mismatch       ok
Creating dump of global objects                             ok
Creating dump of database schemas
                                                             ok
Checking for presence of required libraries                 fatal

Your installation references loadable libraries that are missing from the
new installation.  You can add these libraries to the new installation,
or remove the functions using them from the old installation.  A list of
problem libraries is in the file:
     loadable_libraries.txt

Failure, exiting

root@p2tstl2mondbm:/# cat /home/LAMPIRIS/postgres/loadable_libraries.txt
Could not load library "$libdir/pg_buffercache"
ERROR:  could not access file "$libdir/pg_buffercache": No such file or
directory

Could not load library "$libdir/pg_trgm"
ERROR:  could not access file "$libdir/pg_trgm": No such file or directory

Could not load library "$libdir/uuid-ossp"
ERROR:  could not access file "$libdir/uuid-ossp": No such file or directory

root@p2tstl2mondbm:/#

But the first time it was working, I canceled to find a way ton optimise
the cpu/ram usage of the process...
But now i got the error

Any idea?

Thanks

Matthieu



Le 10/12/14 04:30, Peter Eisentraut a écrit :
> On 12/8/14 2:37 AM, Matthieu Lejeune wrote:
>> I have upgraded the postgresql-common and postgresql-client-common :
>> But I got the same error :
>>
>> root@p2tstl2mondbm:/var/lib# pg_upgradecluster 9.1 main --method=upgrade
>> Disabling connections to the old cluster during upgrade...
>> Restarting old cluster with restricted connections...
>> Stopping old cluster...
>> Creating new cluster 9.3/main ...
>>    config /etc/postgresql/9.3/main
>>    data   /var/lib/postgresql/9.3/main
>>    locale C
>> Flags of /var/lib/postgresql/9.3/main set as ---------------C
>>    port   5433
>> Error: could not create symlink /var/lib/postgresql/9.1/main/pg_ident.conf
>> Re-enabling connections to the old cluster...
>> Error during cluster dumping, removing new cluster
>> pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
>> exist
>> Is server running?
>> Error: could not reload old cluster, please do that manually
> At this point, I think you should add some manual debug statements into
> the script and see what's going on.  The script itself is not very
> complicated, so you can tweak to make it work for you.
>
>
>

On Fri, Dec 12, 2014 at 05:22:29PM +0100, Matthieu Lejeune wrote:
> root@p2tstl2mondbm:/# cat /home/LAMPIRIS/postgres/loadable_libraries.txt
> Could not load library "$libdir/pg_buffercache"
> ERROR:  could not access file "$libdir/pg_buffercache": No such file
> or directory
>
> Could not load library "$libdir/pg_trgm"
> ERROR:  could not access file "$libdir/pg_trgm": No such file or directory
>
> Could not load library "$libdir/uuid-ossp"
> ERROR:  could not access file "$libdir/uuid-ossp": No such file or directory

So you need to install the shared objects into the new cluster that were
used in the old cluster.

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


>
> root@p2tstl2mondbm:/#
>
> But the first time it was working, I canceled to find a way ton
> optimise the cpu/ram usage of the process...
> But now i got the error
>
> Any idea?
>
> Thanks
>
> Matthieu
>
>
>
> Le 10/12/14 04:30, Peter Eisentraut a écrit :
> >On 12/8/14 2:37 AM, Matthieu Lejeune wrote:
> >>I have upgraded the postgresql-common and postgresql-client-common :
> >>But I got the same error :
> >>
> >>root@p2tstl2mondbm:/var/lib# pg_upgradecluster 9.1 main --method=upgrade
> >>Disabling connections to the old cluster during upgrade...
> >>Restarting old cluster with restricted connections...
> >>Stopping old cluster...
> >>Creating new cluster 9.3/main ...
> >>   config /etc/postgresql/9.3/main
> >>   data   /var/lib/postgresql/9.3/main
> >>   locale C
> >>Flags of /var/lib/postgresql/9.3/main set as ---------------C
> >>   port   5433
> >>Error: could not create symlink /var/lib/postgresql/9.1/main/pg_ident.conf
> >>Re-enabling connections to the old cluster...
> >>Error during cluster dumping, removing new cluster
> >>pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
> >>exist
> >>Is server running?
> >>Error: could not reload old cluster, please do that manually
> >At this point, I think you should add some manual debug statements into
> >the script and see what's going on.  The script itself is not very
> >complicated, so you can tweak to make it work for you.
> >
> >
> >
>
>
>
>
> --
> 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

  + Everyone has their own god. +

Do you have a documentation to do this ?

Thanks for your answer


Envoyé de mon iPhone

> Le 12 déc. 2014 à 19:09, Bruce Momjian <bruce@momjian.us> a écrit :
>
>> On Fri, Dec 12, 2014 at 05:22:29PM +0100, Matthieu Lejeune wrote:
>> root@p2tstl2mondbm:/# cat /home/LAMPIRIS/postgres/loadable_libraries.txt
>> Could not load library "$libdir/pg_buffercache"
>> ERROR:  could not access file "$libdir/pg_buffercache": No such file
>> or directory
>>
>> Could not load library "$libdir/pg_trgm"
>> ERROR:  could not access file "$libdir/pg_trgm": No such file or directory
>>
>> Could not load library "$libdir/uuid-ossp"
>> ERROR:  could not access file "$libdir/uuid-ossp": No such file or directory
>
> So you need to install the shared objects into the new cluster that were
> used in the old cluster.
>
> ---------------------------------------------------------------------------
>
>
>>
>> root@p2tstl2mondbm:/#
>>
>> But the first time it was working, I canceled to find a way ton
>> optimise the cpu/ram usage of the process...
>> But now i got the error
>>
>> Any idea?
>>
>> Thanks
>>
>> Matthieu
>>
>>
>>
>> Le 10/12/14 04:30, Peter Eisentraut a écrit :
>>> On 12/8/14 2:37 AM, Matthieu Lejeune wrote:
>>>> I have upgraded the postgresql-common and postgresql-client-common :
>>>> But I got the same error :
>>>>
>>>> root@p2tstl2mondbm:/var/lib# pg_upgradecluster 9.1 main --method=upgrade
>>>> Disabling connections to the old cluster during upgrade...
>>>> Restarting old cluster with restricted connections...
>>>> Stopping old cluster...
>>>> Creating new cluster 9.3/main ...
>>>>  config /etc/postgresql/9.3/main
>>>>  data   /var/lib/postgresql/9.3/main
>>>>  locale C
>>>> Flags of /var/lib/postgresql/9.3/main set as ---------------C
>>>>  port   5433
>>>> Error: could not create symlink /var/lib/postgresql/9.1/main/pg_ident.conf
>>>> Re-enabling connections to the old cluster...
>>>> Error during cluster dumping, removing new cluster
>>>> pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
>>>> exist
>>>> Is server running?
>>>> Error: could not reload old cluster, please do that manually
>>> At this point, I think you should add some manual debug statements into
>>> the script and see what's going on.  The script itself is not very
>>> complicated, so you can tweak to make it work for you.
>>
>>
>>
>>
>> --
>> 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
>
>  + Everyone has their own god. +
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin

On Fri, Dec 12, 2014 at 07:49:09PM +0100, Matthieu Lejeune wrote:
> Do you have a documentation to do this ?

No.  CREATE EXTENSION is that you want, but these would be obvious to
anyone who installed them in the old cluster.

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


>
> Thanks for your answer
>
>
> Envoyé de mon iPhone
>
> > Le 12 déc. 2014 à 19:09, Bruce Momjian <bruce@momjian.us> a écrit :
> >
> >> On Fri, Dec 12, 2014 at 05:22:29PM +0100, Matthieu Lejeune wrote:
> >> root@p2tstl2mondbm:/# cat /home/LAMPIRIS/postgres/loadable_libraries.txt
> >> Could not load library "$libdir/pg_buffercache"
> >> ERROR:  could not access file "$libdir/pg_buffercache": No such file
> >> or directory
> >>
> >> Could not load library "$libdir/pg_trgm"
> >> ERROR:  could not access file "$libdir/pg_trgm": No such file or directory
> >>
> >> Could not load library "$libdir/uuid-ossp"
> >> ERROR:  could not access file "$libdir/uuid-ossp": No such file or directory
> >
> > So you need to install the shared objects into the new cluster that were
> > used in the old cluster.
> >
> > ---------------------------------------------------------------------------
> >
> >
> >>
> >> root@p2tstl2mondbm:/#
> >>
> >> But the first time it was working, I canceled to find a way ton
> >> optimise the cpu/ram usage of the process...
> >> But now i got the error
> >>
> >> Any idea?
> >>
> >> Thanks
> >>
> >> Matthieu
> >>
> >>
> >>
> >> Le 10/12/14 04:30, Peter Eisentraut a écrit :
> >>> On 12/8/14 2:37 AM, Matthieu Lejeune wrote:
> >>>> I have upgraded the postgresql-common and postgresql-client-common :
> >>>> But I got the same error :
> >>>>
> >>>> root@p2tstl2mondbm:/var/lib# pg_upgradecluster 9.1 main --method=upgrade
> >>>> Disabling connections to the old cluster during upgrade...
> >>>> Restarting old cluster with restricted connections...
> >>>> Stopping old cluster...
> >>>> Creating new cluster 9.3/main ...
> >>>>  config /etc/postgresql/9.3/main
> >>>>  data   /var/lib/postgresql/9.3/main
> >>>>  locale C
> >>>> Flags of /var/lib/postgresql/9.3/main set as ---------------C
> >>>>  port   5433
> >>>> Error: could not create symlink /var/lib/postgresql/9.1/main/pg_ident.conf
> >>>> Re-enabling connections to the old cluster...
> >>>> Error during cluster dumping, removing new cluster
> >>>> pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
> >>>> exist
> >>>> Is server running?
> >>>> Error: could not reload old cluster, please do that manually
> >>> At this point, I think you should add some manual debug statements into
> >>> the script and see what's going on.  The script itself is not very
> >>> complicated, so you can tweak to make it work for you.
> >>
> >>
> >>
> >>
> >> --
> >> 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
> >
> >  + Everyone has their own god. +
> >
> >
> > --
> > 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

  + Everyone has their own god. +

Hi,

It's works perfectly
I have forget to install postgresql-contrib

Thanks for your help community

Matthieu

Le 12/12/14 21:36, Bruce Momjian a écrit :
> On Fri, Dec 12, 2014 at 07:49:09PM +0100, Matthieu Lejeune wrote:
>> Do you have a documentation to do this ?
> No.  CREATE EXTENSION is that you want, but these would be obvious to
> anyone who installed them in the old cluster.
>
> ---------------------------------------------------------------------------
>
>
>> Thanks for your answer
>>
>>
>> Envoyé de mon iPhone
>>
>>> Le 12 déc. 2014 à 19:09, Bruce Momjian <bruce@momjian.us> a écrit :
>>>
>>>> On Fri, Dec 12, 2014 at 05:22:29PM +0100, Matthieu Lejeune wrote:
>>>> root@p2tstl2mondbm:/# cat /home/LAMPIRIS/postgres/loadable_libraries.txt
>>>> Could not load library "$libdir/pg_buffercache"
>>>> ERROR:  could not access file "$libdir/pg_buffercache": No such file
>>>> or directory
>>>>
>>>> Could not load library "$libdir/pg_trgm"
>>>> ERROR:  could not access file "$libdir/pg_trgm": No such file or directory
>>>>
>>>> Could not load library "$libdir/uuid-ossp"
>>>> ERROR:  could not access file "$libdir/uuid-ossp": No such file or directory
>>> So you need to install the shared objects into the new cluster that were
>>> used in the old cluster.
>>>
>>> ---------------------------------------------------------------------------
>>>
>>>
>>>> root@p2tstl2mondbm:/#
>>>>
>>>> But the first time it was working, I canceled to find a way ton
>>>> optimise the cpu/ram usage of the process...
>>>> But now i got the error
>>>>
>>>> Any idea?
>>>>
>>>> Thanks
>>>>
>>>> Matthieu
>>>>
>>>>
>>>>
>>>> Le 10/12/14 04:30, Peter Eisentraut a écrit :
>>>>> On 12/8/14 2:37 AM, Matthieu Lejeune wrote:
>>>>>> I have upgraded the postgresql-common and postgresql-client-common :
>>>>>> But I got the same error :
>>>>>>
>>>>>> root@p2tstl2mondbm:/var/lib# pg_upgradecluster 9.1 main --method=upgrade
>>>>>> Disabling connections to the old cluster during upgrade...
>>>>>> Restarting old cluster with restricted connections...
>>>>>> Stopping old cluster...
>>>>>> Creating new cluster 9.3/main ...
>>>>>>   config /etc/postgresql/9.3/main
>>>>>>   data   /var/lib/postgresql/9.3/main
>>>>>>   locale C
>>>>>> Flags of /var/lib/postgresql/9.3/main set as ---------------C
>>>>>>   port   5433
>>>>>> Error: could not create symlink /var/lib/postgresql/9.1/main/pg_ident.conf
>>>>>> Re-enabling connections to the old cluster...
>>>>>> Error during cluster dumping, removing new cluster
>>>>>> pg_ctl: PID file "/var/lib/postgresql/9.1/main/postmaster.pid" does not
>>>>>> exist
>>>>>> Is server running?
>>>>>> Error: could not reload old cluster, please do that manually
>>>>> At this point, I think you should add some manual debug statements into
>>>>> the script and see what's going on.  The script itself is not very
>>>>> complicated, so you can tweak to make it work for you.
>>>>
>>>>
>>>>
>>>> --
>>>> 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
>>>
>>>   + Everyone has their own god. +
>>>
>>>
>>> --
>>> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgsql-admin