On Mon, Apr 4, 2016 at 12:07 PM, Shulgin, Oleksandr <oleksandr.shul...@zalando.de> wrote: > On Apr 4, 2016 17:54, "Robert Haas" <robertmh...@gmail.com> wrote: >> >> On Fri, Apr 1, 2016 at 10:15 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> > Peter Eisentraut <pete...@gmx.net> writes: >> >> I like how browsers show a little lock in the address bar depending on >> >> whether SSL is in use. This could be useful in psql as well. Here is >> >> a >> >> prototype patch. >> >> Comments? >> > >> > -1 on the hard-coded UTF8, even with the encoding check (which I don't >> > think is terribly trustworthy). How about defining it in a way that >> > lets/makes the user provide the character(s) to print? >> >> I think you have been trolled. Note the date. > > Are you trying to say that this feature is in your opinion useless?
Well, what I was trying to say is that I don't think the proposal was 100% serious. However, I also don't think it's particularly useful. I am not a big fan of cluttering up the psql command line with random Unicode glyphs. It's easy enough to find out whether you've got an SSL connection if you want to, with \conninfo. I don't think it needs to be part of every prompt. YMMV, of course. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers