Re: Why an array in pg_group?

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Reinoud van Leeuwen <reinoud(dot)v(at)n(dot)leeuwen(dot)net>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why an array in pg_group?
Date: 2002-11-26 21:05:48
Message-ID: 1038344747.1958.20.camel@rh72.home.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Reinoud van Leeuwen kirjutas K, 20.11.2002 kell 17:03:
> Hi,
>
> Is there any reason why the grolist field in the table pg_group is
> implemented as an array and not as a separate table?

most likely for performance reasons.

> According to the documentation:
>
> <quote source="Postgresql 7.2 User Manual, chapter 6 near the end">
> Arrays are not sets; using arrays in the manner described in the previous
> paragraph is often a sign of database misdesign.
> </quote>
>
> I have trouble implementing a way to easily check whether a user is part
> of a group. (I use Apache::AuthDBI to implement authentication and wanted
> to make a view with columns username, userid , groupname. And installing
> the contrib/array give's me a postgresql that is different from all the
> others :-(

not from those who also have installed contrib/array ;)

but you should actually be using contrib/intagg (and perhaps contrib
intarray) for performance reasons ;)

--
Hannu Krosing <hannu(at)tm(dot)ee>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message scott.marlowe 2002-11-26 21:13:34 Re: [mail] Re: Native Win32 sources
Previous Message Hannu Krosing 2002-11-26 20:59:53 Re: Hirarchical queries a la Oracle. Patch.