From: Shaun Thomas <sthomas@optionshouse.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Performance of pg_basebackup
Date: Tue, 12 Jun 2012 10:00:35 -0500
Message-ID: <4FD75993.5020803@optionshouse.com> (raw)
In-Reply-To: <CABUevEx7Y5RjpJHUR20Xe0OpxD=0QKghu2tyx11EJPk0-15Q_g@mail.gmail.com>
References: <4FD75824.9000005@optionshouse.com>
<CABUevEx7Y5RjpJHUR20Xe0OpxD=0QKghu2tyx11EJPk0-15Q_g@mail.gmail.com>
On 06/12/2012 09:57 AM, Magnus Hagander wrote:
> If you have a single tablespace you can have pg_basebackup write the
> output to stdout and then pipe that through pigz.
Yeah, I saw that. Unfortunately we have tiered storage and hence two
tablespaces. :(
To be fair, my current process cheats by following symlinks. I haven't
yet modified it to explicitly handle tablespaces. I'll probably just
steal the directory method pg_basebackup uses until it can natively call
an external compression program.
Thanks, Magnus!
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sthomas@optionshouse.com, magnus@hagander.net
Subject: Re: Performance of pg_basebackup
In-Reply-To: <4FD75993.5020803@optionshouse.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox