From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
Cc: | "Colin 't Hart" <colin(at)sharpheart(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] psql \n shortcut for set search_path = |
Date: | 2012-07-10 16:00:06 |
Message-ID: | 22660.1341936006@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Josh Kupershmidt <schmiddy(at)gmail(dot)com> writes:
> On Tue, Jul 10, 2012 at 2:09 AM, Colin 't Hart <colin(at)sharpheart(dot)org> wrote:
>> Attached please find a trivial patch for psql which adds a \n meta command
>> as a shortcut for typing set search_path =.
> I think the use-case is a bit narrow: saving a few characters typing
> on a command not everyone uses very often (I don't), at the expense of
> adding yet another command to remember.
Another point here is that we are running low on single-letter backslash
command names in psql. I'm not sure that "SET SEARCH_PATH" is so useful
as to justify using up one of the ones that are left.
ISTM there was some discussion awhile back about user-definable typing
shortcuts in psql. I don't recall any details, but being able to set
up "SET SEARCH_PATH" as a user-definable shortcut if it's useful to you
would eliminate the question about whether it's useful to everyone.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-07-10 16:02:48 | Re: Re: Allow replacement of bloated primary key indexes without foreign key rebuilds |
Previous Message | Bruce Momjian | 2012-07-10 15:50:18 | Using pg_upgrade on log-shipping standby servers |