Re: Patch: Implement failover on libpq connect level.
Tatsuo Ishii <ishii@sraoss.co.jp>
From: Tatsuo Ishii <ishii@sraoss.co.jp>
To: mithun.cy@enterprisedb.com
Cc: robertmhaas@gmail.com, peter.eisentraut@2ndquadrant.com, pvh@pvh.ca,
pgsql-hackers@postgresql.org
Date: 2016-11-16T05:03:44Z
Lists: pgsql-hackers
> JDBC is sending "show transaction_read_only" to find whether it is master > or not. > Victor's patch also started with it, but later it was transformed into > pg_is_in_recovery > by him as it appeared more appropriate to identify the master / slave. In my understanding pg_is_in_recovery() returns true if it's a standby node. However, even if it returns other than true, the server is not necessarily a primary. Even it's not configured as a streaming replication primary, it returns other than true. So if your intention is finding a primary, I am not sure if pg_is_in_recovery() is the best solution. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
Commits
-
libpq: Add target_session_attrs parameter.
- 721f7bd3cbcc 10.0 landed
-
Remove superuser checks in pgstattuple
- fd321a1dfd64 10.0 cited
-
Fix unwanted flushing of libpq's input buffer when socket EOF is seen.
- c405918858c0 9.6.0 cited