From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | kevin brintnall <kbrint(at)rufus(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: GRANT/REVOKE column-level privileges |
Date: | 2006-01-13 15:04:10 |
Message-ID: | 25081.1137164650@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> Umm, yes. You also need to add the column to the contents of
> pg_attribute, give the attribute a number, increase the number of
> attributes as stored in pg_class, update the #define that gives the
> attribute count, change the macro that gives the size of the
> pg_attribute structure (ATTRIBUTE_TUPLE_SIZE) and update all the places
> that create the structure to store a null or something else in that
> column.
> At that, I think I missed some steps but this should get you a bit
> further...
It'd be worthwhile to look into the CVS history to study past commits
that have added columns to pg_attribute. Adding columns to any of
the core system catalogs is generally a PITA ... not impossible,
but there are plenty of details to take care of.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-01-13 15:24:30 | Re: C++ -> C : Module for converting the WHERE clause to the canonical form with PostgreSQL |
Previous Message | pmagnoli | 2006-01-13 14:12:29 | Re: PostgreSQL win32 & NT4 |