Gavin Sherry <[EMAIL PROTECTED]> writes:
> On Thu, 28 Oct 2004, Alvaro Herrera wrote:
>> Ok, so no opinions? Nobody objects to me creating two new shared
>> catalogs to keep track of dependency on global objects, one for
>> user/groups and other for tablespaces?
> Perhaps we could (gulp) reenable
On Thu, 28 Oct 2004, Alvaro Herrera wrote:
> On Thu, Oct 28, 2004 at 01:30:31AM -0300, Alvaro Herrera wrote:
>
> Hi,
>
> > So the first obvious question: should I create two separate catalogs,
> > one for users and other for tablespaces?
>
> Ok, so no opinions? Nobody objects to me creating two n
On Thu, Oct 28, 2004 at 01:30:31AM -0300, Alvaro Herrera wrote:
Hi,
> So the first obvious question: should I create two separate catalogs,
> one for users and other for tablespaces?
Ok, so no opinions? Nobody objects to me creating two new shared
catalogs to keep track of dependency on global
Hackers,
I'm currently playing with implementing a "shared dependency" catalog,
to keep track of objects pointing to global objects, currently users and
tablespaces. So it is forbidden to drop a user that owns tables (or
whatever objects) on other databases.
So far, it works nicely; it lists obj
