Bummer, it looks like there isn't any good solution for the case of
identical user and group names. You might want to search through the
archives to see if this scenario was discussed when roles were being
designed, but it looks like your best bet is to rename either the user
or the group before du
[EMAIL PROTECTED] wrote:
> Which version of pg_dump did you use to dump the old database? The
> recommended procedure is to use the newer version of pg_dump (ie:
> pg_dump from 8.1.1) to dump the old database. It's possible that the
> newer version of pg_dump has facilities in place to deal with th
Which version of pg_dump did you use to dump the old database? The
recommended procedure is to use the newer version of pg_dump (ie:
pg_dump from 8.1.1) to dump the old database. It's possible that the
newer version of pg_dump has facilities in place to deal with this.
Those facilities would obviou
I loaded a 7.4.x dump into a new 8.1.1 database and found out what happens
if you had the same name as both a user and a group. You can get users with
more rights than they had before. I guess it is too late, but perhaps a
mention in the release text would have been a good idea. Advise people to
r
[EMAIL PROTECTED] said:
> I think we're pondering removing the secondary password file feature
> sometime;
The current system allows a particular user (in my case http) to connect to
the database olny from the unix domain socket and no where else. What ever system
is going to replace the secon
--- Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> On Mon, 19 Jun 2000, R D wrote:
>
> > Hi,I need a secondary passwd files because I do
> not
> > know another way to manage user access to DBs.
>
> That's what I thought.
>
> > If there was a pg_shadow in every DB replacing
> external passwd fil
On Mon, 19 Jun 2000, R D wrote:
> Hi,I need a secondary passwd files because I do not
> know another way to manage user access to DBs.
That's what I thought.
> If there was a pg_shadow in every DB replacing external passwd file,
Hmm, that would be in semi-violation of SQL, since users are supp
--- Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> R D writes:
>
> > 1. If I'm using different password files for
> each
> > database can I grant or revoke privileges to this
> > users without creating the same users in pg_user
> > table?
>
> No, you always have to use CREATE USER. Btw., I
> t
R D writes:
> 1. If I'm using different password files for each
> database can I grant or revoke privileges to this
> users without creating the same users in pg_user
> table?
No, you always have to use CREATE USER. Btw., I think we're pondering
removing the secondary password file feature som
Hi there,
i have few questions in users and droups in pgSQL that
i can't check in the next few days and this is
inportant in my choice of database:
1. If I'm using different password files for each
database can I grant or revoke privileges to this
users without creating the same users in pg_user
10 matches
Mail list logo
