Re: PostgreSQL Auditing

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Curtis Ruck <curtis(dot)ruck+pgsql(dot)hackers(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL Auditing
Date: 2016-02-02 20:09:44
Message-ID: 56B10D08.60702@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/2/16 5:00 AM, Simon Riggs wrote:
> Since you've written the email here, I'd ask that you join our community
> and use your knowledge and passion to make things happen.

+1. Kudos for speaking up in the first place, but it's clear that right
now the biggest thing holding Postgres back is lack of reviewers,
followed by lack of developers. If your company put even 10% of what it
would pay for Oracle or MSSQL licensing back into the community (either
via direct employee involvement or by funding development) then auditing
could have moved a lot faster than it did.

It would also help if the community better publicized ways that
companies could give back.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-02-02 20:27:39 Re: Ununsed member in printQueryOpt
Previous Message Tom Lane 2016-02-02 20:02:34 Re: Patch: make behavior of all versions of the "isinf" function be similar