| From: | Gerald Fiedler <gerald(at)interface-business(dot)de> |
|---|---|
| To: | Spirou <spirou(at)carolo(dot)net> |
| Cc: | pgsql-hackers <pgsql-interfaces(at)postgreSQL(dot)org> |
| Subject: | RE: [INTERFACES] [Fwd: bug ? get_groname: group 0 not found] |
| Date: | 1999-09-02 08:51:25 |
| Message-ID: | XFMail.990902105125.gerald@interface-business.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Spirou,
>> ---------------------------
>> INSERT INTO pg_group VALUES ('http_user')
>> CREATE USER "www-data" IN GROUP http_user;
>> CREATE USER nobody IN GROUP http_user;
>>
>> mybase=> select * from pg_group;
>> groname |grosysid|grolist
>> ---------+--------+-------
>> http_user| |
>> (1 row)
>>
>> mybase=> \z
>> NOTICE: get_groname: group 0 not found
>> pqReadData() -- backend closed the channel unexpectedly.
>> This probably means the backend terminated abnormally
>> before or while processing the request.
Please look at my answer for Wim Aarts question "can grolist in pg_group be
updated" in the GENERAL list. There you can found an URL for an administration
tool which handles the group access for you.
Gerald
| From | Date | Subject | |
|---|---|---|---|
| Next Message | postgres | 1999-09-02 09:18:51 | RE: [INTERFACES] [Fwd: bug ? get_groname: group 0 not found] |
| Previous Message | Programmers login | 1999-09-02 07:50:00 | Compiling the ODBC Driver Source |