Re: per user/database connections limit again

From: Petr Jelinek <pjmodos(at)parba(dot)cz>
To: Alvaro Herrera <alvherre(at)surnet(dot)cl>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: per user/database connections limit again
Date: 2005-07-04 11:31:31
Message-ID: 42C91E13.2010704@parba.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Alvaro Herrera wrote:

>I was wondering if there was some way to defer the user check till a
>later time, when the pg_authid relation could be checked? Not sure if
>that's a good idea, but it may help reduce the impact of the change, and
>thus chances that it'd be rejected.
>
>
Well It can, but it would mean one more lock on procarray and I didn't
want that and like I said, MyDatabaseId is read from flatfile too.
Auth flatfile is used only on two other places which I also patched so I
don't see this as a problem (it's used in hba.c to check role membership
and in crypt.c for password verification)

--
Regards
Petr Jelinek (PJMODOS)

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2005-07-04 12:06:29 Re: [HACKERS] HEAD doesn't cope with libraries in non-default
Previous Message Hannu Krosing 2005-07-04 11:26:54 Re: PATCH to allow concurrent VACUUMs to not lock each