| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: Uppercase tab completion keywords in psql? |
| Date: | 2012-03-23 15:07:24 |
| Message-ID: | CAEYLb_Uwm52Fuxhbqk6C_x+3_xuNLR2M+aRd3291J7rBo-CMzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22 March 2012 22:05, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
> On 03/22/2012 05:49 PM, Bruce Momjian wrote:
>>
>>
>> Robert Haas and I are disappointed by this change. I liked the fact
>> that I could post nice-looking SQL queries without having to use my
>> capslock key (which I use as a second control key). Any chance of
>> reverting this change?
>>
>
> Should it be governed by a setting?
Perhaps, but I find the behaviour that was introduced by Peter's patch
to be a more preferable default.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-03-23 15:11:13 | Re: patch for parallel pg_dump |
| Previous Message | Alvaro Herrera | 2012-03-23 15:02:18 | Re: heap_freeze_tuple locking requirements |