Re: pg_upgrade link mode - Mailing list pgsql-general

From AI Rumman
Subject Re: pg_upgrade link mode
Date
Msg-id CAGoODpdBw3H9SW2v+vpgptg+_mmE1jx5uCP83NZ9PPtfmMKe1Q@mail.gmail.com
Whole thread Raw
In response to pg_upgrade link mode  (Fabio Rueda Carrascosa <avances123@gmail.com>)
Responses Re: pg_upgrade link mode
List pgsql-general
I always think its a bit risky to use link instead of copying. However, I'd suggest to try the  --check at first of pg_upgrade.


On Thu, May 16, 2013 at 1:42 PM, Fabio Rueda Carrascosa <avances123@gmail.com> wrote:
Hello, I have a 9.1 cluster with 50 databases, only one table per db with 2000 rows only, but a lot of schema around each one (postgis databases)

The old cluster size is 1GB

du -chs /var/lib/postgresql/9.1/main/
1.1G

now I run a pg_upgrade to 9.2 with hard link mode,

pg_upgrade  --link \
    --old-datadir=/var/lib/postgresql/9.1/main \
    --new-datadir=/var/lib/postgresql/9.2/main \
    --old-bindir=/usr/lib/postgresql/9.1/bin \
    --new-bindir=/usr/lib/postgresql/9.2/bin

du -chs /var/lib/postgresql/9.2/main/
880M


Is the expected behaviour? I can't double the space in production.

Thanks.

pgsql-general by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: 9.3 beta and materialized views
Next
From: Kevin Grittner
Date:
Subject: Re: 9.3 beta and materialized views