Received: from hub.org.org (localhost [127.0.0.1]) by hub.org (8.10.1/8.11.0) with SMTP id e9I4YIW92873 for ; Wed, 18 Oct 2000 00:34:18 -0400 (EDT) (envelope-from pgsql-docs-owner@hub.org) Received: from localhost.localdomain (IDENT:root@pere.dialup.ee.uwa.edu.au [130.95.70.69]) by hub.org (8.10.1/8.11.0) with ESMTP id e9I4QeW89679 for ; Wed, 18 Oct 2000 00:26:41 -0400 (EDT) (envelope-from pere@hungry.com) Received: (from pere@localhost) by localhost.localdomain (8.9.3/8.9.3) id MAA06748; Wed, 18 Oct 2000 12:26:34 +0800 Date: Wed, 18 Oct 2000 12:26:34 +0800 Message-Id: <200010180426.MAA06748@localhost.localdomain> X-Authentication-Warning: localhost.localdomain: pere set sender to pere@hungry.com using -f To: pgsql-docs@postgresql.org Subject: Re: Question on comment From: Petter Reinholdtsen In-reply-to: <3953.971842693@sss.pgh.pa.us> X-Archive-Number: 200010/20 X-Sequence-Number: 335 > IIRC, the COMMENT command was added in 7.0. But it's just a user > interface to the pg_description table, which has existed for awhile. > pg_description is the thing to look at if you want to manipulate > comments directly. Basically it maps OIDs to comments... Hm, OK. How are the access rights to this table when 'comment on' is used? I remember trying earlier to use this table to store comments, but discovered each user had to have write access, even to add comments on their own tables. Is this problem fixed? -- ##> Petter Reinholdtsen <## | pere@td.org.uit.no