Date: Wed, 21 Jan 2015 23:19:12 -0500
From: Bruce Momjian <bruce@momjian.us>
To: Craig James <cjames@emolecules.com>
Cc: Matheus de Oliveira <matioli.matheus@gmail.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: pg_basebackup bug: base backup is double the size of the database
Message-ID: <20150122041912.GC27757@momjian.us>
References: 
 <CAFwQ8reMSPCeWH+n_LrZeLg=auQh4LiypKhcYGaROdnxet9mYw@mail.gmail.com>
 <CAJghg4Lqpc9RE-W1x-ufbjjRX2Kry7M68dqp1gSFOwhoq9tEJA@mail.gmail.com>
 <CAFwQ8rfsnZUXt2N1R8vOtmLuvx4FXmzJ5Jrq5YwkRpWefNGRAw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAFwQ8rfsnZUXt2N1R8vOtmLuvx4FXmzJ5Jrq5YwkRpWefNGRAw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On Wed, Jan 21, 2015 at 11:01:15AM -0800, Craig James wrote:
>     If I'm not overlooking, then neither barman nor pg_basebackup is to blame,
>     but whoever created the hard links; if PostgreSQL did this (which I doubt)
>     then it is a bug.
> 
> 
> As I said, I absolutely didn't create these links. I never, ever monkey with
> the innards of the Postgres tablespaces. Never have, never will.  It had to be
> done by Postgres, pg_upgrade or some other Postgres binary.

If you used --link mode, it does create hard links between the old and
new clusters, which is clearly documented.

-- 
  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