From: Pepe TD Vo <pepevo@yahoo.com>
To: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: Amine Tengilimoglu <aminetengilimoglu@gmail.com>
Cc: Pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: how to fail over slave to master
Date: Mon, 28 Dec 2020 19:24:03 +0000 (UTC)
Message-ID: <1299392843.3134647.1609183443761@mail.yahoo.com> (raw)
In-Reply-To: <EB6C684E-31DE-4C3D-A96A-3561529F9A6D@elevated-dev.com>
References: <984856653.599807.1609180184705.ref@mail.yahoo.com>
<984856653.599807.1609180184705@mail.yahoo.com>
<CADTdw-yhihjbQ7VEvKtqdBEUV9XEbd6fq+JfHtesF3f+Pk7Fzw@mail.gmail.com>
<611218422.3134435.1609181699910@mail.yahoo.com>
<EB6C684E-31DE-4C3D-A96A-3561529F9A6D@elevated-dev.com>
In verison 12, postgresql.auto.conf to replace recovery.conf
do I need to run
1. pg_ctl promote -D Pg_data (in slave?)2. pg_rewind --target -pg_data=master_server (aliase hostname of master) --source-server="port=5433 user=replica dbname=postgres" --progress3. change postgresql.cond parameter, primary_slot_name ='main'
do I need to run pg_rewind for each dbname? I don't understand why pg_rewind set the port=5433 not 5432?
Bach-Nga
No one in this world is pure and perfect. If you avoid people for their mistakes you will be alone. So judge less, love, and forgive more.To call him a dog hardly seems to do him justice though in as much as he had four legs, a tail, and barked, I admit he was, to all outward appearances. But to those who knew him well, he was a perfect gentleman (Hermione Gingold)
**Live simply **Love generously **Care deeply **Speak kindly.*** Genuinely rich *** Faithful talent *** Sharing success
On Monday, December 28, 2020, 02:10:14 PM EST, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
> On Dec 28, 2020, at 11:54 AM, Pepe TD Vo <pepevo@yahoo.com> wrote:
>
> Version 12 and can you show me step by step what needs to do? I found a document in version 10 to promote salve to master with pg_ctl and create recovery.conf. Recovery.conf is not existed in version 12 but in version 1.
1) The parameters that used to be set in recovery.conf are instead set in postgresql.conf in 12 & above.
2) They are set on your replica; otherwise it would not come up as a replica. They are not needed in a master.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pepevo@yahoo.com, scott_ribe@elevated-dev.com, aminetengilimoglu@gmail.com
Subject: Re: how to fail over slave to master
In-Reply-To: <1299392843.3134647.1609183443761@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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