pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPg-Upgrade standbys via rsync... and avoid sending UNlogged data?
15+ messages / 4 participants
[nested] [flat]
* Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-07-22 23:29 Jerry Sievers <gsievers19@comcast.net>
0 siblings, 2 replies; 15+ messages in thread
From: Jerry Sievers @ 2016-07-22 23:29 UTC (permalink / raw)
To: pgsql-admin
Has anyone found a clever way to $subject that doesn't involved
calculating which are all of the files unnecessary to send and then
running rsync with an exclude list?
I'm pondering this right now.
ISTM for each unlogged table/index/toast in pg_class where
relpersistence='u'...
rsync --exclude-from... (and exclude-from-file contains)
*/base/$dbid/$relfilenode
*/base/$dbid/$relfilenode.*
*/base/$dbid/$relfilenode_*
...
The leading * will match the old/new data directoryes being sent to the
standby.
MAster upgrade is done using hard-links and the rsync method generally
as per the pg docs.
I have among others, a 5TB system w/about 40G of unlogged data.
The rsync method of upgrade takes only several seconds during a snapshot
based test however as the snap was off a live system, the crash recovery
startup trunc'd all the unlogged data.
This will not be the case during the real upgrade and I just as soon
avoid sending the unlogged data only to have it trunc'd away as soon as
the standby is started after the upgrade.
Thanks
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-07-22 23:43 Bruce Momjian <bruce@momjian.us>
parent: Jerry Sievers <gsievers19@comcast.net>
1 sibling, 1 reply; 15+ messages in thread
From: Bruce Momjian @ 2016-07-22 23:43 UTC (permalink / raw)
To: Jerry Sievers <gsievers19@comcast.net>; +Cc: pgsql-admin
On Fri, Jul 22, 2016 at 06:29:05PM -0500, Jerry Sievers wrote:
> Has anyone found a clever way to $subject that doesn't involved
> calculating which are all of the files unnecessary to send and then
> running rsync with an exclude list?
>
> I'm pondering this right now.
>
> ISTM for each unlogged table/index/toast in pg_class where
> relpersistence='u'...
>
> rsync --exclude-from... (and exclude-from-file contains)
>
> */base/$dbid/$relfilenode
> */base/$dbid/$relfilenode.*
> */base/$dbid/$relfilenode_*
> ...
>
> The leading * will match the old/new data directoryes being sent to the
> standby.
>
> MAster upgrade is done using hard-links and the rsync method generally
> as per the pg docs.
>
> I have among others, a 5TB system w/about 40G of unlogged data.
>
> The rsync method of upgrade takes only several seconds during a snapshot
> based test however as the snap was off a live system, the crash recovery
> startup trunc'd all the unlogged data.
>
> This will not be the case during the real upgrade and I just as soon
> avoid sending the unlogged data only to have it trunc'd away as soon as
> the standby is started after the upgrade.
Good question --- I don't think there is an easy answer except to
truncate the unlogged tables before the upgrade.
--
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 +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-07-25 16:22 Jerry Sievers <gsievers19@comcast.net>
parent: Bruce Momjian <bruce@momjian.us>
0 siblings, 0 replies; 15+ messages in thread
From: Jerry Sievers @ 2016-07-25 16:22 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Jerry Sievers <gsievers19@comcast.net>; pgsql-admin
Bruce Momjian <bruce@momjian.us> writes:
> On Fri, Jul 22, 2016 at 06:29:05PM -0500, Jerry Sievers wrote:
>
>> Has anyone found a clever way to $subject that doesn't involved
>> calculating which are all of the files unnecessary to send and then
>> running rsync with an exclude list?
>>
>> I'm pondering this right now.
>>
>> ISTM for each unlogged table/index/toast in pg_class where
>> relpersistence='u'...
>>
>> rsync --exclude-from... (and exclude-from-file contains)
>>
>> */base/$dbid/$relfilenode
>> */base/$dbid/$relfilenode.*
>> */base/$dbid/$relfilenode_*
>> ...
>>
>> The leading * will match the old/new data directoryes being sent to the
>> standby.
>>
>> MAster upgrade is done using hard-links and the rsync method generally
>> as per the pg docs.
>>
>> I have among others, a 5TB system w/about 40G of unlogged data.
>>
>> The rsync method of upgrade takes only several seconds during a snapshot
>> based test however as the snap was off a live system, the crash recovery
>> startup trunc'd all the unlogged data.
>>
>> This will not be the case during the real upgrade and I just as soon
>> avoid sending the unlogged data only to have it trunc'd away as soon as
>> the standby is started after the upgrade.
>
> Good question --- I don't think there is an easy answer except to
> truncate the unlogged tables before the upgrade.
Yup, as I suspected.
My data warehouse team *rather* not have to dirive the unlogged data
again since it takes time... and I rather not needlessly replicate it
during upgrade (er, because that takes time.)
At my company, if we choose to not avoid replicating unlogged data *and*
run for a short interval in production without a standby, snapshot the
halted master and take the rsync off of that meanwhile the master is
back online.
I'll figure something out.
Thanks!
--
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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-07-25 16:37 Stephen Frost <sfrost@snowman.net>
parent: Jerry Sievers <gsievers19@comcast.net>
1 sibling, 1 reply; 15+ messages in thread
From: Stephen Frost @ 2016-07-25 16:37 UTC (permalink / raw)
To: Jerry Sievers <gsievers19@comcast.net>; +Cc: pgsql-admin
* Jerry Sievers (gsievers19@comcast.net) wrote:
> Has anyone found a clever way to $subject that doesn't involved
> calculating which are all of the files unnecessary to send and then
> running rsync with an exclude list?
>
> I'm pondering this right now.
Certainly an interesting issue to consider. I have to admit that I
hadn't considered unlogged tables when working out how to do the
hard-link-based approach.
> ISTM for each unlogged table/index/toast in pg_class where
> relpersistence='u'...
>
> rsync --exclude-from... (and exclude-from-file contains)
>
> */base/$dbid/$relfilenode
> */base/$dbid/$relfilenode.*
> */base/$dbid/$relfilenode_*
> ...
>
> The leading * will match the old/new data directoryes being sent to the
> standby.
You would have to address tablespaces too, if you have any.
> 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.
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-07-25 16:43 Stephen Frost <sfrost@snowman.net>
parent: Stephen Frost <sfrost@snowman.net>
0 siblings, 1 reply; 15+ messages in thread
From: Stephen Frost @ 2016-07-25 16:43 UTC (permalink / raw)
To: Jerry Sievers <gsievers19@comcast.net>; +Cc: pgsql-admin
* 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. :)
Depends on your network speed if the 40G would be an issue or not then.
In some cases, it might only add a bit of time but keep the process
simple, other cases, it might take longer. I'm not really thrilled with
the idea of complicating the rsync in that way, but I can understand why
you're considering it.
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-07-25 17:34 Jerry Sievers <gsievers19@comcast.net>
parent: Stephen Frost <sfrost@snowman.net>
0 siblings, 1 reply; 15+ messages in thread
From: Jerry Sievers @ 2016-07-25 17:34 UTC (permalink / raw)
To: Stephen Frost <sfrost@snowman.net>; +Cc: Jerry Sievers <gsievers19@comcast.net>; pgsql-admin
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.
Thanks!
> Depends on your network speed if the 40G would be an issue or not then.
> In some cases, it might only add a bit of time but keep the process
> simple, other cases, it might take longer. I'm not really thrilled with
> the idea of complicating the rsync in that way, but I can understand why
> you're considering it.
>
> Thanks!
>
> Stephen
--
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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-07-26 16:19 Bruce Momjian <bruce@momjian.us>
parent: Jerry Sievers <gsievers19@comcast.net>
0 siblings, 2 replies; 15+ messages in thread
From: Bruce Momjian @ 2016-07-26 16:19 UTC (permalink / raw)
To: Jerry Sievers <gsievers19@comcast.net>; +Cc: Stephen Frost <sfrost@snowman.net>; pgsql-admin
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.
--
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 +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-07-26 17:22 Jerry Sievers <gsievers19@comcast.net>
parent: Bruce Momjian <bruce@momjian.us>
1 sibling, 0 replies; 15+ messages in thread
From: Jerry Sievers @ 2016-07-26 17:22 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Jerry Sievers <gsievers19@comcast.net>; Stephen Frost <sfrost@snowman.net>; pgsql-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
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-07-26 23:11 Stephen Frost <sfrost@snowman.net>
parent: Bruce Momjian <bruce@momjian.us>
1 sibling, 1 reply; 15+ messages in thread
From: Stephen Frost @ 2016-07-26 23:11 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Jerry Sievers <gsievers19@comcast.net>; pgsql-admin
* 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.
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-08-04 22:55 Bruce Momjian <bruce@momjian.us>
parent: Stephen Frost <sfrost@snowman.net>
0 siblings, 1 reply; 15+ messages in thread
From: Bruce Momjian @ 2016-08-04 22:55 UTC (permalink / raw)
To: Stephen Frost <sfrost@snowman.net>; +Cc: Jerry Sievers <gsievers19@comcast.net>; pgsql-admin
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 +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Attachments:
rsync.diff (text/x-diff, 676B) download
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,
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-08-05 13:04 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
parent: Bruce Momjian <bruce@momjian.us>
0 siblings, 1 reply; 15+ messages in thread
From: Peter Eisentraut @ 2016-08-05 13:04 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; Stephen Frost <sfrost@snowman.net>; +Cc: Jerry Sievers <gsievers19@comcast.net>; pgsql-admin
On 8/4/16 6:55 PM, Bruce Momjian wrote:
> <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,
That seems like an odd location to insert that.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-08-05 14:05 Bruce Momjian <bruce@momjian.us>
parent: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 1 reply; 15+ messages in thread
From: Bruce Momjian @ 2016-08-05 14:05 UTC (permalink / raw)
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>; +Cc: Stephen Frost <sfrost@snowman.net>; Jerry Sievers <gsievers19@comcast.net>; pgsql-admin
On Fri, Aug 5, 2016 at 09:04:19AM -0400, Peter Eisentraut wrote:
> On 8/4/16 6:55 PM, Bruce Momjian wrote:
> > <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,
>
> That seems like an odd location to insert that.
Would you like to suggest another location as I could not find out.
--
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 +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-08-05 14:06 Bruce Momjian <bruce@momjian.us>
parent: Bruce Momjian <bruce@momjian.us>
0 siblings, 1 reply; 15+ messages in thread
From: Bruce Momjian @ 2016-08-05 14:06 UTC (permalink / raw)
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>; +Cc: Stephen Frost <sfrost@snowman.net>; Jerry Sievers <gsievers19@comcast.net>; pgsql-admin
On Fri, Aug 5, 2016 at 10:05:21AM -0400, Bruce Momjian wrote:
> On Fri, Aug 5, 2016 at 09:04:19AM -0400, Peter Eisentraut wrote:
> > On 8/4/16 6:55 PM, Bruce Momjian wrote:
> > > <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,
> >
> > That seems like an odd location to insert that.
>
> Would you like to suggest another location as I could not find out.
Sorry, typo: :-(
Would you like to suggest another location as I could not find one.
--
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 +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-08-08 01:29 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
parent: Bruce Momjian <bruce@momjian.us>
0 siblings, 1 reply; 15+ messages in thread
From: Peter Eisentraut @ 2016-08-08 01:29 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Stephen Frost <sfrost@snowman.net>; Jerry Sievers <gsievers19@comcast.net>; pgsql-admin
On 8/5/16 10:06 AM, Bruce Momjian wrote:
> On Fri, Aug 5, 2016 at 10:05:21AM -0400, Bruce Momjian wrote:
>> On Fri, Aug 5, 2016 at 09:04:19AM -0400, Peter Eisentraut wrote:
>>> On 8/4/16 6:55 PM, Bruce Momjian wrote:
>>>> <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,
>>>
>>> That seems like an odd location to insert that.
>>
>> Would you like to suggest another location as I could not find out.
>
> Sorry, typo: :-(
>
> Would you like to suggest another location as I could not find one.
I think it belongs to the previous paragraph, so I moved it there.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 15+ messages in thread
* Re: Pg-Upgrade standbys via rsync... and avoid sending UNlogged data?
@ 2016-08-08 20:46 Bruce Momjian <bruce@momjian.us>
parent: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 0 replies; 15+ messages in thread
From: Bruce Momjian @ 2016-08-08 20:46 UTC (permalink / raw)
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>; +Cc: Stephen Frost <sfrost@snowman.net>; Jerry Sievers <gsievers19@comcast.net>; pgsql-admin
On Sun, Aug 7, 2016 at 09:29:20PM -0400, Peter Eisentraut wrote:
> On 8/5/16 10:06 AM, Bruce Momjian wrote:
> > On Fri, Aug 5, 2016 at 10:05:21AM -0400, Bruce Momjian wrote:
> >> On Fri, Aug 5, 2016 at 09:04:19AM -0400, Peter Eisentraut wrote:
> >>> On 8/4/16 6:55 PM, Bruce Momjian wrote:
> >>>> <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,
> >>>
> >>> That seems like an odd location to insert that.
> >>
> >> Would you like to suggest another location as I could not find out.
> >
> > Sorry, typo: :-(
> >
> > Would you like to suggest another location as I could not find one.
>
> I think it belongs to the previous paragraph, so I moved it there.
OK, fine.
--
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 +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 15+ messages in thread
end of thread, other threads:[~2016-08-08 20:46 UTC | newest]
Thread overview: 15+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-07-22 23:29 Pg-Upgrade standbys via rsync... and avoid sending UNlogged data? Jerry Sievers <gsievers19@comcast.net>
2016-07-22 23:43 ` Bruce Momjian <bruce@momjian.us>
2016-07-25 16:22 ` Jerry Sievers <gsievers19@comcast.net>
2016-07-25 16:37 ` Stephen Frost <sfrost@snowman.net>
2016-07-25 16:43 ` Stephen Frost <sfrost@snowman.net>
2016-07-25 17:34 ` Jerry Sievers <gsievers19@comcast.net>
2016-07-26 16:19 ` Bruce Momjian <bruce@momjian.us>
2016-07-26 17:22 ` Jerry Sievers <gsievers19@comcast.net>
2016-07-26 23:11 ` Stephen Frost <sfrost@snowman.net>
2016-08-04 22:55 ` Bruce Momjian <bruce@momjian.us>
2016-08-05 13:04 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2016-08-05 14:05 ` Bruce Momjian <bruce@momjian.us>
2016-08-05 14:06 ` Bruce Momjian <bruce@momjian.us>
2016-08-08 01:29 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2016-08-08 20:46 ` Bruce Momjian <bruce@momjian.us>
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