Message-ID: <4FD75993.5020803@optionshouse.com>
Date: Tue, 12 Jun 2012 10:00:35 -0500
From: Shaun Thomas <sthomas@optionshouse.com>
Reply-To: <sthomas@optionshouse.com>
Organization: Peak6
User-Agent: Mozilla/5.0 (X11; Linux i686;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Magnus Hagander <magnus@hagander.net>
CC: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Performance of pg_basebackup
References: <4FD75824.9000005@optionshouse.com>
	<CABUevEx7Y5RjpJHUR20Xe0OpxD=0QKghu2tyx11EJPk0-15Q_g@mail.gmail.com>
In-Reply-To: 
 <CABUevEx7Y5RjpJHUR20Xe0OpxD=0QKghu2tyx11EJPk0-15Q_g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
content-transfer-encoding: 7bit

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