Skip site navigation (1) Skip section navigation (2)

Re: Patch to add support for security labels on local objects

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Patch to add support for security labels on local objects
Date: 2011-07-25 16:17:40
Message-ID: 1311610661.22497.3.camel@laptop (view raw or flat)
Thread:
Lists: pgadmin-hackers
On Sun, 2011-07-24 at 21:23 +0200, Guillaume Lelarge wrote:
> On Sun, 2011-07-24 at 17:40 +0200, Guillaume Lelarge wrote:
> > On Sun, 2011-07-24 at 10:58 +0200, Guillaume Lelarge wrote:
> > > Hi,
> > > 
> > > This patch adds support to a PostgreSQL 9.1 feature called security
> > > labels. It adds a new tab to tables, columns, aggregates, domains,
> > > foreign tables, functions, languages, sequences, types, and views
> > > dialogs, that allows one to add security label for each provider they
> > > want. I suppose most users will have only one provider, but the patch
> > > supports multi providers.
> > > 
> > > Note that this does not support a recent 9.2 feature of PostgreSQL that
> > > adds security labels to global objects. This will be part of another
> > > patch.
> > > 
> > > 
> > 
> > Because of the latest push I did, it won't apply cleanly. There is one
> > small issue which will be easy to fix.
> > 
> 
> While working on it, I thought I would better look at the same time at
> supporting security labels for global/shared objects. So, here are two
> patches. The first one is a revised version of the previous patch. It
> fixes the apply issue, and it deals better with connections. The second
> one supports security labels for global objects.
> 
> 

Commited.


-- 
Guillaume
  http://blog.guillaume.lelarge.info
  http://www.dalibo.com


In response to

Responses

pgadmin-hackers by date

Next:From: pgAdmin TracDate: 2011-07-25 16:20:43
Subject: Re: [pgAdmin III] #322: CHECK constraints with NOT VALID
Previous:From: Guillaume LelargeDate: 2011-07-25 16:17:31
Subject: Re: Load/Save feature for the database designer

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group