Some errata and round up comments.
First of all, I think it's relevant to give some info about the system
I'm running:
OS: Linux
Distro: Gentoo
Perl: dev-lang/perl-5.12.3-r1 USE="-* berkdb gdbm"
Gentoo Base System release: 2.0.2
PORTDIR/metadata/timestamp.chk: Tue, 12 Jul 2011 00:45:01 +
2011/9/28, Merlin Moncure :
>
> I disagree. unnest() and array_agg() (or, even better, array()
> constructor syntax) are an absolute joy to work with and thinking in a
> more functional way, which is usually the key to making things run
> quickly. Also both functions are trivial to emulate in use
On Wed, Sep 28, 2011 at 11:45 AM, Diego Augusto Molina
wrote:
> 2011/9/28, Merlin Moncure :
>> Yup -- I get it now. Well, one point about this is that it seems
>> directed towards your personal requirements. This is a very 'heavy'
>> audit system that will not be suitable for high performance
>>
2011/9/28, Merlin Moncure :
> Yup -- I get it now. Well, one point about this is that it seems
> directed towards your personal requirements. This is a very 'heavy'
> audit system that will not be suitable for high performance
> transactional systems. That said, it looks well thought out. Storin
On Wed, Sep 28, 2011 at 8:20 AM, Diego Augusto Molina
wrote:
> 2011/9/27, Merlin Moncure :
>> *) when posting schema definitions, particularly in email format, try
>> not to use dumped definitions from pg_dump or pgadmin. This creates a
>> lot of noise in the script that detracts from what you are
2011/9/27, Merlin Moncure :
> *) when posting schema definitions, particularly in email format, try
> not to use dumped definitions from pg_dump or pgadmin. This creates a
> lot of noise in the script that detracts from what you are trying to
> do. Also an attached file would probably have been m
On Tue, Sep 27, 2011 at 04:52:08PM -0300, Diego Augusto Molina wrote:
> 2011/9/27, Diego Augusto Molina :
> > Honestly, I don't remember why I used triggers instead of rules in the
> > "audit" and "audet" tables.
>
> I remember now, that's because in my case, operations over tuples are
> done very
2011/9/27 Diego Augusto Molina :
> /* Created by Diego Augusto Molina in 2011 for Tucuman
> Government,
> Argentina. */
OK, few random comments:
*) when posting schema definitions, particularly in email format, try
not to use dumped definitions from pg_dump or pgadmin. This creat
2011/9/27, Diego Augusto Molina :
> Honestly, I don't remember why I used triggers instead of rules in the
> "audit" and "audet" tables.
I remember now, that's because in my case, operations over tuples are
done very lightly (one or two in the same sentence at a time). So, for
a case as such, rule
Sh*#@, the code was wrapped! if you can suggest me an external web to
host the code I can put it there and send the link.
Maybe the wiki
Nevertheless, I can't seem to publish in the wiki. I think I've
followed all the steps but still can't.
Anyway, there aren't many long-long lines, excep
/* Created by Diego Augusto Molina in 2011 for Tucuman
Government,
Argentina. */
/*
-- Execute the following accordingly to your needs.
CREATE TRUSTED PROCEDURAL LANGUAGE 'plpgsql';
CREATE TRUSTED PROCEDURAL LANGUAGE 'plperl';
*/
CREATE ROLE auditor NOSUPERUSER NOINHERIT
2011/9/27 Diego Augusto Molina
> Hi, I had to implement a logging system for some DBs in work. It's
> generic and implemented using plperl. I've seen tons of mails on the
> list from newbies asking for something like this using plpgsql, but no
> specific solution is pointed for them. I think this
12 matches
Mail list logo
