Date: Thu, 4 Aug 2016 18:55:36 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Jerry Sievers <gsievers19@comcast.net>, pgsql-admin@postgresql.org
Subject: Re: Pg-Upgrade standbys via rsync... and avoid sending
 UNlogged data?
Message-ID: <20160804225536.GA22579@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>
 <20160726231129.GH4028@tamriel.snowman.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="bp/iNruPH9dso1Pn"
Content-Disposition: inline
In-Reply-To: <20160726231129.GH4028@tamriel.snowman.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org


--bp/iNruPH9dso1Pn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Jul 26, 2016 at 07:11:29PM -0400, Stephen Frost wrote:
> * Bruce Momjian (bruce@momjian.us) wrote:
> > 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.
> 
> It'd probably be good to document what happens with unlogged tables.

Attached patch applied to head.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+                     Ancient Roman grave inscription +

--bp/iNruPH9dso1Pn
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="rsync.diff"

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
new file mode 100644
index fcc94ee..7f1c52a
*** a/doc/src/sgml/ref/pgupgrade.sgml
--- b/doc/src/sgml/ref/pgupgrade.sgml
*************** rsync --archive --delete --hard-links --
*** 504,509 ****
--- 504,511 ----
        </para>
  
        <para>
+        Unfortunately, <application>rsync</> also needlessly copies the
+        files associated with temporary and unlogged tables.
         If you have tablespaces, you will need to run a similar
         <application>rsync</> command for each tablespace directory.  If you
         have relocated <filename>pg_xlog</> outside the data directories,

--bp/iNruPH9dso1Pn
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


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

--bp/iNruPH9dso1Pn--