Re: PostgreSQL Auditing

Поиск
Список
Период
Сортировка
От Joshua D. Drake
Тема Re: PostgreSQL Auditing
Дата
Msg-id 56B0CA27.6030106@commandprompt.com
обсуждение исходный текст
Ответ на Re: PostgreSQL Auditing  (José Luis Tallón <jltallon@adv-solutions.net>)
Ответы Re: PostgreSQL Auditing  (Michael Banck <michael.banck@credativ.de>)
Re: PostgreSQL Auditing  (curtis.ruck@gmail.com)
Список 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.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: Support for N synchronous standby servers - take 2
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [PATCH] Refactoring of LWLock tranches