Bruce Momjian wrote:
> Bruce Momjian wrote:
>> Alvaro Herrera wrote:
>>> Tom Lane escribi?:
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I don't know of a way to make MD5 and db_user_namespace work cleanly so
> we are considering removing db_user_namespace in 8.4.
We are? It's no
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Tom Lane escribi?:
> > > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > > I don't know of a way to make MD5 and db_user_namespace work cleanly so
> > > > we are considering removing db_user_namespace in 8.4.
> > >
> > > We are? It's no more or les
Fernando Moreno wrote:
> Thanks for the answers, I wasn't aware of the conflict between md5-auth and
> db_user_namespace, but it seems highly related to my problem.
>
> Could you suggest me another way to handle this? Managing users in the usual
> way is likely to work fine most of the time, but n
2008/10/7 Alvaro Herrera <[EMAIL PROTECTED]>
> Bruce Momjian escribió:
>
> > Well, I posted about this in August with no one replying:
> >
> > http://archives.postgresql.org/pgsql-admin/2008-08/msg00068.php
> >
> > Basically, there is a mismatch between what libpq and the backend think
> > i
Bruce Momjian escribió:
> Well, I posted about this in August with no one replying:
>
> http://archives.postgresql.org/pgsql-admin/2008-08/msg00068.php
>
> Basically, there is a mismatch between what libpq and the backend think
> is the username, and that affects how MD5 uses the salt on t
Alvaro Herrera wrote:
> Tom Lane escribi?:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > I don't know of a way to make MD5 and db_user_namespace work cleanly so
> > > we are considering removing db_user_namespace in 8.4.
> >
> > We are? It's no more or less ugly than the day it was put in (
Tom Lane escribió:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I don't know of a way to make MD5 and db_user_namespace work cleanly so
> > we are considering removing db_user_namespace in 8.4.
>
> We are? It's no more or less ugly than the day it was put in (the
> MD5 encryption option was al
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I don't know of a way to make MD5 and db_user_namespace work cleanly so
> we are considering removing db_user_namespace in 8.4.
We are? It's no more or less ugly than the day it was put in (the
MD5 encryption option was already there).
If we had some i
Bruce Momjian wrote:
Is there a way to avoid this problem without having to reset all passwords
or storing them in plain text?
I don't know of a way to make MD5 and db_user_namespace work cleanly so
we are considering removing db_user_namespace in 8.4.
I would +1 the removal.
Joshua D. Dr
Fernando Moreno wrote:
> Hi there, I'm going to use the db_user_namespace parameter to get a strong
> relationship between roles and databases, multiple databases -users
> included- residing in the same server without conflicts is my objective too.
>
>
> Right now I'm working on the backup proces
Hi there, I'm going to use the db_user_namespace parameter to get a strong
relationship between roles and databases, multiple databases -users
included- residing in the same server without conflicts is my objective too.
Right now I'm working on the backup process, which ideally would let me
mirro
On Sat, May 27, 2006 at 01:39:18PM +0200, Rafal Pietrak wrote:
> Hi All,
>
> Having the new (as of rel 8.xx) ROLE system; whould it be a problem to
> implement a:
>
> GRANT/REVOKE CONNECT ON "database" TO/FROM "role" | PUBLIC;
>
> instead of current cludge of "db_user_namespace"?
A patch
Hi All,
Having the new (as of rel 8.xx) ROLE system; whould it be a problem to
implement a:
GRANT/REVOKE CONNECT ON "database" TO/FROM "role" | PUBLIC;
instead of current cludge of "db_user_namespace"?
--
-R
---(end of broadcast)---
TIP
Uh, no one has come up with a better solution, so it will be in 7.4 too.
---
Sean Mullen wrote:
>
> What is the 'status' of DB_USER_NAMESPACE?
>
> Is it still a temporary measure and is it safe to rely on it?
>
>
> Sean.
What is the 'status' of DB_USER_NAMESPACE?
Is it still a temporary measure and is it safe to rely on it?
Sean.
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
15 matches
Mail list logo
