| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data? |
| Date: | 2016-07-26 16:19:46 |
| Message-ID: | 20160726161946.GA3511@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Jul 25, 2016 at 12:34:45PM -0500, Jerry Sievers wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>
> > * Stephen Frost (sfrost(at)snowman(dot)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.
--
Bruce Momjian <bruce(at)momjian(dot)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 +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jerry Sievers | 2016-07-26 17:22:39 | Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data? |
| Previous Message | Guillaume Lelarge | 2016-07-26 11:55:51 | Re: if anyone is running slony, I have a trivial question |