From: Richard Huxton <dev@archonet.com>
To: jtayamai <jtayamai@googlemail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Encryption in the tables of a Postgres 7.3.2 database
Date: Fri, 11 Sep 2009 08:26:17 +0100
Message-ID: <4AA9FB99.6090107@archonet.com> (raw)
In-Reply-To: <cad8465b-4892-435f-bb4f-171e1bc307fb@o41g2000yqb.googlegroups.com>
References: <cad8465b-4892-435f-bb4f-171e1bc307fb@o41g2000yqb.googlegroups.com>
jtayamai wrote:
> Hi,
>
> I've a Postgres DB release 7.3.2 and some developed C++ and PHP code
> so as to communicate with it.
Most important thing: upgrade this version of PostgreSQL. You can't even
get 7.3 from the main site any more, so you'll have to look on
ftp://ftp-archives.postgresql.org/
The last release was 7.3.21 - work through the release notes and then
download as soon as possible.
> Currently, the data I've in the different tables is stored with no
> encription at all, and I was wondering if there would be an easy way
> to get it encrypted without major changes in the already developed C++/
> PHP code.
>
> I mean, I want to replace the non-encrypted database with an encrypted
> version of it without C++/PHP programmes noticing it.
>
> Has anyone any suggestion about the easiest way to do it?
Well, you don't want to be making any changes to a PostgreSQL version
that old - it will be impossible to find anyone to help with it. I'd
suggest encrypting a filesystem and putting your database on that. That
will impact performance of course.
If you only want to encrypt a few tables, you could look at splitting
where the files are stored. That might involve setting up symlinks, I
can't remember if 7.3 supported tablespaces.
If you do put some files on the encrypted filesystem and some on the
unencrypted one make sure you don't start PG until both are available. I
don't know what would happen if one wasn't but it's unlikely to be fun.
--
Richard Huxton
Archonet Ltd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: dev@archonet.com, jtayamai@googlemail.com
Subject: Re: Encryption in the tables of a Postgres 7.3.2 database
In-Reply-To: <4AA9FB99.6090107@archonet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox