Re: pg_upgrade link mode

From: AI Rumman <rummandba(at)gmail(dot)com>
To: Fabio Rueda Carrascosa <avances123(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_upgrade link mode
Date: 2013-05-16 17:56:05
Message-ID: CAGoODpdBw3H9SW2v+vpgptg+_mmE1jx5uCP83NZ9PPtfmMKe1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmail(dot)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.
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2013-05-16 17:59:34 Re: 9.3 beta and materialized views
Previous Message Thomas Kellerer 2013-05-16 17:48:33 Re: 9.3 beta and materialized views