Re: FWD: Re: Updated backslash consistency patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: FWD: Re: Updated backslash consistency patch
Date
Msg-id 603c8f070901211210x1433b95di4dd356ebb69d4444@mail.gmail.com
Whole thread Raw
In response to Re: FWD: Re: Updated backslash consistency patch  (Bruce Momjian <bruce@momjian.us>)
Responses Re: FWD: Re: Updated backslash consistency patch  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
> Here are the items I think are best to default to user-only:
[...]
> Here are the ones that should include system objects by default:

Well, at a minimum, I think it's important for any type of object to
have an easy way to exclude system objects, because "show me all of
the stuff that didn't come with the database" is a valid use case for
any type of item.

It's certainly true that the more obscure the item is, the more likely
you are to be looking for the system object rather than a user object.But it's really subjective where to put the line:
somepeople might
 
put it between table and function (Tom), others might put it between
function and aggregate (Bruce), and still others might say there's no
object type so exotic that I don't want system objects excluded by
default (me).  And there isn't any right or wrong answer here: it's
just opinions.

So maybe we should provide U, S, and A modifiers for every type of
object (user, system, all).  That doesn't solve the problem of which
should be the default for each object type, but at least it guarantees
that you can type an extra character to get the behavior you want in
any particular case.

...Robert


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Pluggable Indexes
Next
From: Alvaro Herrera
Date:
Subject: Re: reducing statistics write overhead