Re: FWD: Re: Updated backslash consistency patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: FWD: Re: Updated backslash consistency patch
Date: 2009-01-16 01:25:52
Message-ID: 16821.1232069152@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> gah, I find that to be terrible. If we wanted to compromise, I'd
> rather have \df do what it does today, to keep backwards-compat and
> not confuse users, and \dfU to do what I want 99% of the time.

This seems to me to be the compromise most likely to dissatisfy everyone
the least ...

> On a seperate (kind of) note, I'd really like to be able to say "I want
> this function visible everywhere" like a system function.

Huh? System functions don't have that property either.

You could do that today with a quick hack on your default search path,
though: set search_path = global, pg_catalog, public or something like
that (... and be *very* careful about what you put in schema "global").

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-01-16 01:40:28 Re: Hot Standby dev build (v8)
Previous Message Josh Berkus 2009-01-16 01:24:23 Re: FWD: Re: Updated backslash consistency patch