From: Gone, Sajan <SGone@lb.com>
To: Samed YILDIRIM <samed@reddoc.net>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Postgres replication
Date: Wed, 19 Apr 2017 15:00:27 +0000
Message-ID: <D51CF18A.69C0%sgone@lb.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Hi,
The replication worked fine until the server re-start on Master we did recently this morning. After the restart of the linux server, I have started the database backup on Master however when I logged on to the slave server I saw the replication is terminated between the master and the slave.
Here is the status of the slave when I queried pg_stat_replication table:
postgres=# select * from pg_stat_replication ;
pid | usesysid | usename | application_name | client_addr | client_hostname | client_port | backend_start | backend_xmin | state
| sent_location | write_location | flush_location | replay_location | sync_priority | sync_state
-----+----------+---------+------------------+-------------+-----------------+-------------+---------------+--------------+-------
+---------------+----------------+----------------+-----------------+---------------+------------
(0 rows)
Does we have to re-initiate the replication every time on postgres if we restart either the Master/Slave Server. If so how can I re-initiate the replication.
Please let me know your thoughts on this.
Thank You,
Sajan Gone
Database Administrator
L Brands
Mobile #: 517-990-5282
Office #: 614-577-7622
From: Samed YILDIRIM <samed@reddoc.net<mailto:samed@reddoc.net>>
Date: Friday, April 14, 2017 at 10:34 AM
To: Sajan Gone <sgone@lb.com<mailto:sgone@lb.com>>, "pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>" <pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>>
Subject: Re: [ADMIN] Postgres replication
Hi Sajan,
You can use following query.
select * from pg_stat_replication;
Best regards.
Samed YILDIRIM
14.04.2017, 17:20, "Gone, Sajan" <sgone@lb.com<mailto:sgone@lb.com>>:
Hi Samed,
Thanks for sending out the weblink. I was able to successfully set the replication up (Master/Slave, Hot stand by).
I really appreciate your help on this.
My background is mostly on MySQL so my next question would be on how to look at the replication status. Like MySQL “Show slave status \G” command is there any command on postgres to look at the slave current status(or replication status).
Thank You,
Sajan Gone.
From: Samed YILDIRIM <samed@reddoc.net<mailto:samed@reddoc.net>>
Date: Thursday, April 13, 2017 at 4:27 PM
To: Sajan Gone <sgone@lb.com<mailto:sgone@lb.com>>, "pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>" <pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>>
Subject: Re: [ADMIN] Postgres replication
Hi Sajan,
You can take a look following document. It is good for a start point.
https://www.digitalocean.com/community/tutorials/how-to-set-up-master-slave-replication-on-postgresq...;
Best regards.
22:25, 13 Nisan 2017, "Gone, Sajan" <sgone@lb.com<mailto:sgone@lb.com>>:
Hello,
Good afternoon everyone.
This is Sajan Gone, I am trying to setup a Standard Master/Salve replication between two postgres instances. I am pretty much new to postgres and not exactly sure how replication works and what is an architecture behind
it. As of now I am following the standard postgres documentation @ https://www.postgresql.org/docs/current/static/warm-standby.html#PREPARING-MASTER-FOR-STANDBY<htt...;,
however it is slightly difficult for me to understand.
It would be very helpful if any one could guide me in a proper way on setting up Master/Slave replication on postgres. Any recommendations on good documentation
or study materials on postgres replication would be highly appreciated.
Many Thanks in advance.
Thank You,
Sajan Gone
________________________________
Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LB may, for
any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices.
________________________________
Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LB may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices.
________________________________
Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LB may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices.
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: SGone@lb.com, samed@reddoc.net
Subject: Re: Postgres replication
In-Reply-To: <D51CF18A.69C0%sgone@lb.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