Re: Crypto - Mailing list pgsql-hackers

From Marcos Luis Ortiz Valmaseda
Subject Re: Crypto
Date
Msg-id 1295954822.1118611253381220855.JavaMail.root@ucimail4.uci.cu
Whole thread Raw
In response to Re: Crypto  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I think the same, These are not arguments to include crypto on the core, due to then all users have to think on this
aspectto build a simple database, so we would be obligating to the users to use this module. 

I´d let this module on the contrib

Regards

"The hurry is enemy of the success: for that reason.......Be patient"

Ing. Marcos L. Ortiz Valmaseda
Línea Soporte y Despliegue
Centro de Tecnologías de Almacenamiento y Análisis de Datos (CENTALAD)

Linux User # 418229
PostgreSQL User
http://www.postgresql.org
http://www.planetpostgresql.org/
http://www.postgresql-es.org/


----- Mensaje original -----
De: "Tom Lane" <tgl@sss.pgh.pa.us>
Para: "David Fetter" <david@fetter.org>
CC: "Andrew Dunstan" <andrew@dunslane.net>, "PG Hackers" <pgsql-hackers@postgresql.org>
Enviados: Sábado, 19 de Septiembre 2009 6:33:36 GMT -10:00 Hawai
Asunto: Re: [HACKERS] Crypto

David Fetter <david@fetter.org> writes:
> On Sat, Sep 19, 2009 at 11:50:35AM -0400, Andrew Dunstan wrote:
>> What benefit would we  gain from making general crypto part of the
>> core?

> People may wish to encrypt things in the database.

That is not an argument why it has to be in core rather than an add-on.
        regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Standalone backends run StartupXLOG in an incorrect environment
Next
From: Tom Lane
Date:
Subject: Re: updated join removal patch