| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Thomas Munro <munro(at)ip9(dot)org>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cluster name in ps output |
| Date: | 2014-07-04 14:33:43 |
| Message-ID: | 20134.1404484423@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> writes:
>> You mean that if synchronous_standby_names is an empty it automatically
>> should be set to cluster_name?
> No, I mean that synchronous_standby_names should look at cluster_name
> first, and if it's not set then unfortunately look at application_name
> for backward compatibility.
I think you're failing to explain yourself very well. What you really
mean is that we should use cluster_name not application_name to determine
the name that a standby server reports to the master.
There's something to that, perhaps, but I think that the mechanism we use
for doing the reporting involves the application_name parameter passed
through libpq. It might be a bit painful to change that, and I'm not
entirely sure it'd be less confusing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-07-04 14:53:15 | Re: No toast table for pg_shseclabel but for pg_seclabel |
| Previous Message | Tom Lane | 2014-07-04 14:10:20 | Re: Issue while calling new PostgreSQL command from a Java Application |