Re: pgaudit - an auditing extension for PostgreSQL - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: pgaudit - an auditing extension for PostgreSQL
Date
Msg-id CAFcNs+p=eLyCn_iRhfS21MdX4_LTPmb5B+kb01TVn5dmDj1z7A@mail.gmail.com
Whole thread Raw
In response to Re: pgaudit - an auditing extension for PostgreSQL  (David Fetter <david@fetter.org>)
List pgsql-hackers
<div dir="ltr"><div class="gmail_extra"><br />On Wed, Oct 8, 2014 at 2:55 AM, David Fetter <<a
href="mailto:david@fetter.org">david@fetter.org</a>>wrote:<br />><br />> On Wed, Oct 08, 2014 at 12:41:46AM
-0300,Fabrízio de Royes Mello wrote:<br />> > On Wed, Oct 8, 2014 at 12:36 AM, Josh Berkus <<a
href="mailto:josh@agliodbs.com">josh@agliodbs.com</a>>wrote:<br />> > ><br />> > > On 10/07/2014
09:44AM, Fabrízio de Royes Mello wrote:<br />> > > > We can think in a mechanism to create "properties /
options"and assign<br />> > it<br />> > > > to objects (table, index, column, schema, ...) like
COMMENTdoes.<br />> > > ><br />> > > > A quickly thought:<br />> > > ><br />>
>> > CREATE OPTION [ IF NOT EXISTS ] name<br />> > > >     VALIDATOR valfunction<br />> >
>>     [ DEFAULT value ];<br />> > > ><br />> > > > ALTER TABLE name<br />> > >
>    SET OPTION optname { TO | = } { value | 'value' | DEFAULT };<br />> > > ><br />> > > >
It'sjust a simple thought of course. We must think better about the<br />> > syntax<br />> > > > and
purposes.<br/>> > ><br />> > > If we're going to do this (and it seems like a good idea), we
really,<br/>> > > really, really need to include some general system views which expose<br />> > >
theoptions in a user-friendly format (like columns, JSON or an array).<br />> > >  It's already very hard for
usersto get information about what<br />> > > reloptions have been set.<br />> > ><br />> ><br
/>>> Maybe into "information_schema" ??<br />><br />> Not there.  The information schema is defined pretty
preciselyin the<br />> SQL standard and contains only some of this kind of information.<br />><br /><br
/></div><divclass="gmail_extra">You're absolutely right.. thanks...<br /><br /></div><div class="gmail_extra"><br
/>>pg_catalog seems like a much more appropriate space for<br />> PostgreSQL-specific settings.<br />><br
/><br/></div><div class="gmail_extra">We can add views and some functions to get this info too.<br /></div><div
class="gmail_extra"><br/></div><div class="gmail_extra">Regards,<br /></div><div class="gmail_extra"><br />--<br
/>Fabríziode Royes Mello<br />Consultoria/Coaching PostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog: <a
href="http://fabriziomello.github.io">http://fabriziomello.github.io</a><br/>>> Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a><br/>>> Github: <a
href="http://github.com/fabriziomello">http://github.com/fabriziomello</a></div></div>

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Wait free LW_SHARED acquisition - v0.2
Next
From: Marti Raudsepp
Date:
Subject: Re: UPSERT wiki page, and SQL MERGE syntax