Quick coding question with acl fixes

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Quick coding question with acl fixes
Date: 2004-07-25 03:33:38
Message-ID: 41032A12.6040304@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Usually i'd ply away at this one until I figured it out, but we're
running out of time :)

If I have the nspForm variable (which is a Form_pg_namespace) struct
pointer, then how do I check if the nspacl field is default (ie.
"NULL"). This is so I can avoid running DatumGetAclP on it, which seems
to cause alloc error reports.

gdb seems to think it's "$3 = {126}", and that doesn't seem to be NULL
or Datum(0) or anything. Anyone know the answer?

Also, there is an implementation question?

When I run through the acl changing all references from the old owner to
the new owner, should I combine the resulting acls if possible? Because
if the new owner already has some acls on that item, they will end up
with two acls.

Chris

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-07-25 03:48:12 Re: Quick coding question with acl fixes
Previous Message Tom Lane 2004-07-25 03:22:59 Planning for beta (was Re: Sketch of extending error handling for subtransactions)