| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Craig James <cjames(at)emolecules(dot)com> |
| Cc: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup bug: base backup is double the size of the database |
| Date: | 2015-01-22 04:19:12 |
| Message-ID: | 20150122041912.GC27757@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G Johnston | 2015-01-22 06:02:26 | Re: pg_basebackup bug: base backup is double the size of the database |
| Previous Message | Bruce Momjian | 2015-01-22 04:18:17 | Re: pg_basebackup bug: base backup is double the size of the database |