| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Feature request: make cluster_name GUC useful for psql prompts |
| Date: | 2016-05-06 12:21:55 |
| Message-ID: | f88d13f5-51f0-8754-90a3-2728e6bb0f3f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/5/16 9:21 PM, Steve Crawford wrote:
> Adding an escape sequence that references cluster_name would enable
> prompts to identify the cluster in a manner that is both consistent and
> distinct regardless of access path.
I think that would be a good idea. You could probably design it so that
any server parameter reported to the client can be put in a psql prompt.
> Potential issues/improvements:
>
> What should the escape-sequence display if cluster_name is not set or
> the cluster is a pre-9.5 version. %M? %m?
>
> In future server versions should there be a default for cluster_name if
> it is not set? If so, what should it be? Would the server canonical
> hostname + listen-port be reasonable?
Those are good questions. I don't really like the proposed answers,
because that could cause confusion in practical use.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2016-05-06 12:30:31 | Re: psql :: support for \ev viewname and \sv viewname |
| Previous Message | Alex Ignatov | 2016-05-06 08:13:37 | Re: Is pg_control file crashsafe? |