From: | "Colin 't Hart" <colin(at)sharpheart(dot)org> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] psql \n shortcut for set search_path = |
Date: | 2012-07-10 16:26:22 |
Message-ID: | CAMon-aQthOOmOOkURxYY0n5dLQRTQn9kLOZVFQxNi6MZ_Xmv2A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10 July 2012 18:24, David Fetter <david(at)fetter(dot)org> wrote:
> On Tue, Jul 10, 2012 at 12:00:06PM -0400, Tom Lane wrote:
> > 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.
>
> In some sense, we already have them:
>
> \set FOO 'SELECT * FROM pg_stat_activity;'
> ...
> :FOO
>
> Was there more to it?
>
Can I pass a parameter to ":FOO" ?
Cheers,
Colin
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2012-07-10 16:29:24 | Re: Using pg_upgrade on log-shipping standby servers |
Previous Message | Bruce Momjian | 2012-07-10 16:26:09 | Re: Using pg_upgrade on log-shipping standby servers |