Re: psql SET/RESET/SHOW tab completion

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql SET/RESET/SHOW tab completion
Date: 2005-08-14 17:18:33
Message-ID: 791.1124039913@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark <gsstark(at)mit(dot)edu> writes:
> I'm not sure if you're interested, but my 2c speaking as a user would be for
> tab completion to include all variables.

OK, I'm clearly outvoted on this one. How about we make SHOW
tab-complete everything listed in pg_settings, while SET/RESET
tab-complete everything that's USERSET or SUSET?

(We could probably even make it suppress SUSET if you aren't superuser,
but I'm not sure if that's worth the trouble.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas F. O'Connell 2005-08-14 19:45:21 Re: Simplifying wal_sync_method
Previous Message Tom Lane 2005-08-14 16:56:06 Re: PATCH to allow concurrent VACUUMs to not lock each