Re: PostgreSQL Auditing

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: José Luis Tallón <jltallon(at)adv-solutions(dot)net>, Curtis Ruck <curtis(dot)ruck+pgsql(dot)hackers(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PostgreSQL Auditing
Date: 2016-02-02 15:24:23
Message-ID: 56B0CA27.6030106@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/02/2016 02:47 AM, José Luis Tallón wrote:
> On 02/02/2016 02:05 AM, Curtis Ruck wrote:
>> [snip]
>>
>> P.S., do you know what sucks, having a highly performant PostGIS
>> database that works great, and being told to move to Oracle or SQL
>> Server (because they have auditing). Even though they charge extra
>> for Geospatial support (seriously?) or when they don't even have
>> geospatial support (10 years ago). My customer would prefer to
>> re-engineer software designed around PostgreSQL and pay the overpriced
>> licenses, than not have auditing. I agree that their cost analysis is
>> probably way off, even 10 years later, my only solution would be to
>> move to Oracle, SQL Server, a NoSQL solution, or pay EnterpriseDB for
>> their 2 year old version that doesn't have all the cool/modern jsonb
>> support.

PostgreSQL has auditing. It is available now, just not in core. Postgis
isn't available in core either and it seems to do just fine.

JD

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-02-02 15:29:06 Re: [PATCH] Refactoring of LWLock tranches
Previous Message Masahiko Sawada 2016-02-02 15:13:07 Re: Support for N synchronous standby servers - take 2