tag:blogger.com,1999:blog-2095009998266493615.post1189923873435504562..comments2023-07-12T02:39:28.134-07:00Comments on Simple PostgreSQL Blog: Is it failback or switchover with PostgreSQL? Ah, maybe not...Baji Shaikhttp://www.blogger.com/profile/15132725823431299637noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-2095009998266493615.post-38410514198636025322017-09-23T23:46:51.554-07:002017-09-23T23:46:51.554-07:00This post will be very helpful for the begaineer S...This post will be very helpful for the begaineer SEO worker who are new in this field.<br />Keep posting this type of helpful post.<br />With best wishes.<a href="https://warezkeys.com/timeline-maker-pro-4-1-crack-with-patch-license-key/" rel="nofollow">Timeline Maker Pro 4.1</a>Wolfram Mathematica 11 Crack + Activationhttps://www.blogger.com/profile/03826563234844441712noreply@blogger.comtag:blogger.com,1999:blog-2095009998266493615.post-33476870086510204622015-09-21T02:35:21.322-07:002015-09-21T02:35:21.322-07:00Hi Craig Ringer,
How can we handle the automatic ...Hi Craig Ringer,<br /><br />How can we handle the automatic failback in PostgreSQL when we have configures the hot-standby Streaming replication .My client was asking me for solution for Smooth Failover and failback features in PostgreSQL.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2095009998266493615.post-27352101555993709032014-03-31T23:50:06.898-07:002014-03-31T23:50:06.898-07:00Thank you Alexey, Nice tool from Heikki. I will lo...Thank you Alexey, Nice tool from Heikki. I will look at it.Baji Shaikhttps://www.blogger.com/profile/15132725823431299637noreply@blogger.comtag:blogger.com,1999:blog-2095009998266493615.post-17120733267867643512014-03-31T11:06:07.854-07:002014-03-31T11:06:07.854-07:00I think it's actually safe to do with pg_rewin...I think it's actually safe to do with pg_rewind as well in 9.3, if (and only if) you enable wal_log_hints or use data checksums. But only with those.<br /><br />The method suggested here is definitely very likely to cause corruption. It's enough that any background operation runs in between, such as autovacuum, generating any WAL at all.<br /><br />Another safe way is to shut down the old master *first*. That should ensure that no WAL can be created in the "fork".<br /><br />(I would also advice you to look at pg_ctl promote as the recommended way to do failover, rather than trigger files)Magnus Haganderhttps://www.blogger.com/profile/00190230225365745225noreply@blogger.comtag:blogger.com,1999:blog-2095009998266493615.post-84657789657164559032014-03-30T20:21:10.224-07:002014-03-30T20:21:10.224-07:00This looks like an exceptionally bad idea to attem...This looks like an exceptionally bad idea to attempt in production on any kind of data you care about even slightly.<br /><br />The only safe failback (that doesn't involve a totally new pg_basebackup) in 9.4 and below is to stop the old master, make sure WAL archiving is enabled on the old master, pg_start_backup on the new master, rsync from new master to old, pg_stop_backup on the new master, and start the old master up as a replica with a recovery.conf. <br /><br />There's been discussion on ways to do this safely in the next version but I don't think it's gone far yet.Craig Ringerhttps://www.blogger.com/profile/02343803844223399065noreply@blogger.comtag:blogger.com,1999:blog-2095009998266493615.post-39507974307062261662014-03-30T10:54:08.667-07:002014-03-30T10:54:08.667-07:00Look at pg_rewind tool which allow rewinding old m...Look at pg_rewind tool which allow rewinding old master to new slave. http://www.youtube.com/watch?v=wcwh0icr9GMAlexeyhttps://www.blogger.com/profile/09418624687521812667noreply@blogger.comtag:blogger.com,1999:blog-2095009998266493615.post-24247111132467839952014-03-30T04:11:42.550-07:002014-03-30T04:11:42.550-07:00Do I assume correctly that this will only work as ...Do I assume correctly that this will only work as long as no transaction commits on the "old master" after the trigger file has been created? In that case you have to be careful that the cluster is completely quiesced before creating the trigger file.<br /><br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2095009998266493615.post-33759565694513958552014-03-30T03:15:38.535-07:002014-03-30T03:15:38.535-07:00And how safe is this method, exactly? I'm not...And how safe is this method, exactly? I'm not sure how good an idea it is to have these kind of posts indexed by Google, since someone somewhere might actually do it with their data and end up with a broken replica.Anonymousnoreply@blogger.com