pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedupgrades and streaming replication
3+ messages / 3 participants
[nested] [flat]
* upgrades and streaming replication
@ 2013-09-11 03:13 Charles Sprickman <spork@biglist.com>
2013-09-11 10:06 ` Re: upgrades and streaming replication raghu ram <raghuchennuru@gmail.com>
2013-09-20 17:26 ` Re: upgrades and streaming replication Grant Fisher <gfisher@pecanstreet.org>
0 siblings, 2 replies; 3+ messages in thread
From: Charles Sprickman @ 2013-09-11 03:13 UTC (permalink / raw)
To: pgsql-admin
I just wanted to check if there are any updates on the preferred way to upgrade a group of servers that are using streaming replication with minimal downtime.
Mailing list messages from a year or two ago pretty much state the following:
* No current plans to come up with some new mechanism to automate this process, downtime is assumed.
* If you want no downtime, use one of the userspace replication solutions.
* Best option is to upgrade the master with pg_upgrade, then upgrade the slaves and re-copy your data.
* While it's tempting to think you could just run pg_upgrade on all hosts to avoid the copy step, that will not work as something in the system catalog changes which will break replication.
* No good options to speed up the slave copy - rsync will either use timestamps to figure out if a file changed (and streaming skews that), or checksumming (and checksumming is slow).
Is that still pretty much the situation today with 9.2 and 9.3?
Any good guides or BCPs for the standard procedure that emphasize limiting downtime and giving a good rollback path?
Thanks,
Charles
--
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] 3+ messages in thread
* Re: upgrades and streaming replication
2013-09-11 03:13 upgrades and streaming replication Charles Sprickman <spork@biglist.com>
@ 2013-09-11 10:06 ` raghu ram <raghuchennuru@gmail.com>
1 sibling, 0 replies; 3+ messages in thread
From: raghu ram @ 2013-09-11 10:06 UTC (permalink / raw)
To: Charles Sprickman <spork@biglist.com>; +Cc: pgsql-admin
On Wed, Sep 11, 2013 at 8:43 AM, Charles Sprickman <spork@biglist.com>wrote:
> I just wanted to check if there are any updates on the preferred way to
> upgrade a group of servers that are using streaming replication with
> minimal downtime.
>
> Mailing list messages from a year or two ago pretty much state the
> following:
>
> * No current plans to come up with some new mechanism to automate this
> process, downtime is assumed.
> * If you want no downtime, use one of the userspace replication solutions.
> * Best option is to upgrade the master with pg_upgrade, then upgrade the
> slaves and re-copy your data.
> * While it's tempting to think you could just run pg_upgrade on all hosts
> to avoid the copy step, that will not work as something in the system
> catalog changes which will break replication.
> * No good options to speed up the slave copy - rsync will either use
> timestamps to figure out if a file changed (and streaming skews that), or
> checksumming (and checksumming is slow).
>
> Is that still pretty much the situation today with 9.2 and 9.3?
>
> Any good guides or BCPs for the standard procedure that emphasize limiting
> downtime and giving a good rollback path?
>
>
Below URL provides more information about the list of PostgreSQL
Up-gradation methods:
http://www.pateldenish.com/2012/10/an-easy-way-to-reduce-outage-window-for-postgresql-upgrade.html
--Raghu
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: upgrades and streaming replication
2013-09-11 03:13 upgrades and streaming replication Charles Sprickman <spork@biglist.com>
@ 2013-09-20 17:26 ` Grant Fisher <gfisher@pecanstreet.org>
1 sibling, 0 replies; 3+ messages in thread
From: Grant Fisher @ 2013-09-20 17:26 UTC (permalink / raw)
To: Charles Sprickman <spork@biglist.com>; +Cc: pgsql-admin
On Tue, Sep 10, 2013 at 10:13 PM, Charles Sprickman <spork@biglist.com>wrote:
> I just wanted to check if there are any updates on the preferred way to
> upgrade a group of servers that are using streaming replication with
> minimal downtime.
> <snip>
> * No good options to speed up the slave copy - rsync will either use
> timestamps to figure out if a file changed (and streaming skews that), or
> checksumming (and checksumming is slow).
> <snip>
> Is that still pretty much the situation today with 9.2 and 9.3?
>
Charles,
I am also concerned about upgrading our 9.2 servers which are set up using
streaming replication. I would prefer not to copy the data over via rsync,
since that is pretty time consuming. Does anybody know if there any other
options to do an in-place upgrade?
Thanks,
Grant
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2013-09-20 17:26 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-09-11 03:13 upgrades and streaming replication Charles Sprickman <spork@biglist.com>
2013-09-11 10:06 ` raghu ram <raghuchennuru@gmail.com>
2013-09-20 17:26 ` Grant Fisher <gfisher@pecanstreet.org>
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