From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | Vik Fearing <vik(at)2ndquadrant(dot)fr> |
Cc: | Bertrand Paquet <bertrand(dot)paquet(at)doctolib(dot)fr>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Replication |
Date: | 2016-06-06 07:54:31 |
Message-ID: | CAD21AoCdugbzq8Hc37f58T-8D8JCLYq=EBCxYYoYT+b61PZY0w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Jun 4, 2016 at 10:58 PM, Vik Fearing <vik(at)2ndquadrant(dot)fr> wrote:
> On 02/06/16 15:32, Bertrand Paquet wrote:
>> Hi,
>>
>> On an hot standby streaming server, is there any way to know, in SQL, to
>> know the ip of current master ?
>
> No.
>
>> The solution I have is to read the recovery.conf file to find
>> primary_conninfo,
>
> That is currently the only solution. There are plans to allow SQL
> access to the parameters in recovery.conf (or to merge them into
> postgresql.conf) but that's not currently possible.
>
It might not be a right way but how about using pg_read_file()?
postgres(1)=# select regexp_replace(pg_read_file('recovery.conf'),
'.*primary_conninfo = (.*)', '\1');
regexp_replace
---------------------------------------------------
'host=localhost port=5550 application_name=node1'+
(1 row)
You can get the master server information via SQL from standby server.
Regards,
--
Masahiko Sawada
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2016-06-06 08:22:50 | Re: Replication |
Previous Message | Michael Paquier | 2016-06-06 02:24:19 | Re: WAL's listing in pg_xlog by some sql query |