pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jerry Sievers <gsievers19@comcast.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Jerry Sievers <gsievers19@comcast.net>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
Date: Tue, 26 Jul 2016 12:22:39 -0500
Message-ID: <86h9bciaao.fsf@jerry.enova.com> (raw)
In-Reply-To: <20160726161946.GA3511@momjian.us>
References: <86d1m5b6bi.fsf@jerry.enova.com>
	<20160725163700.GZ4028@tamriel.snowman.net>
	<20160725164329.GA4028@tamriel.snowman.net>
	<86eg6hr58q.fsf@jerry.enova.com>
	<20160726161946.GA3511@momjian.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Bruce Momjian <bruce@momjian.us> writes:

> On Mon, Jul 25, 2016 at 12:34:45PM -0500, Jerry Sievers wrote:
>
>> Stephen Frost <sfrost@snowman.net> writes:
>> 
>> > * Stephen Frost (sfrost@snowman.net) wrote:
>> >
>> >> > I have among others, a 5TB system  w/about 40G of unlogged data.
>> >> 
>> >> Honestly, sending an extra 40G out of 5TB (we're talking less than 1%
>> >> here...) might be worth it to keep the process simple.
>> >
>> > Of course, I realize right after sending this that you aren't sending
>> > the 5TB. :)
>> 
>> Roger that!  Really, the hard link pg-upgrade option and rsync method
>> for standbys is pure beauty :-)
>> 
>> We have only the post-analyze and this unlogged data  problem to deal
>> with. 
>> 
>> The warehouse is our only system with any substantial amount of unlogged
>> data.
>> 
>> Reducing post-analyze delay was solved by me here with our groovy
>> threaded AnalyzMaTron.  I can get a >5TB system done in about 45 minutes
>> w/20 threads.
>
> The only thing I can suggest is to document this limitation, if people
> think it is worth it.

+1

A couple sentences right near the rsync piece in pg_upgrade docs would
 do it.

Caveat:UNNLogged data will be unnecessarily transfered via rsync and
then immediately discarded from standbys when the standbys are started
unless those tables are truncated on the master before the upgrade.

-- 
Jerry Sievers
e: jerry.sievers@comcast.net
p: 312.241.7800


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (15+ messages)  latest in thread

Message-ID: <86h9bciaao.fsf@jerry.enova.com>
Permalink:  ../86h9bciaao.fsf@jerry.enova.com/
Also on:    postgresql.org/message-id/86h9bciaao.fsf@jerry.enova.com

 · 

reply

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-admin@postgresql.org
  Cc: gsievers19@comcast.net, bruce@momjian.us, sfrost@snowman.net
  Subject: Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
  In-Reply-To: <86h9bciaao.fsf@jerry.enova.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