[GENERAL] Using pgcrypto with AES-256 bits?

[Stas Oskin]

Hello.

 

I
tried the pgcrypto contrib module with the AES default encryption. It works
pretty nice, but I understand that it's using 128 bit key strength. Is there
any built-in support for the 256 bit key strength? Or it should be used via
external libraries?

 

AFAIK,
the support of mhash and mcrypt was dropped from the recent version of the
module, so the AES 256 functionality can be only provided by OpenSSL?

 

Thank
you.

 

Stas.

[GENERAL] Blob data type and it's efficiency on PostgreSQL

[Stas Oskin]

Hi.

 

We
are using PostgreSQL as the RDBMS for our product, and are very happy with it.
Recently, we have encountered a need to store a lot of binary files, mainly
images (up to ~100,000 files, with sizes varying from 300K-2MB).

 

The
question is, how well PostgreSQL performs with the blob data type, and is it practical
to store these files as blobs?

 

Thanks
in advance,

Stas
Oskin.

[GENERAL] Postgres locks table schema?

[Stas Oskin]

Hi.

 

When running SQL scripts, which change the tables' schema,
we sometimes experience a lock of these tables' schema. The lock occurs on the
first command of the script, on the first modified table. When this occurs, no
further schema modification for this table is possible, until the server is
restarted, which is very problematic for a production environment.

 

Perhaps someone is familiar with this behavior, and how it
can be resolved, without the restart of the server?

 

The server used is PostgreSQL 8.0.3, and the OS is Fedora
Core 3.

 

Thanks.

 

Stas Oskin.

Re: [GENERAL] Postgres locks table schema?

[Stas Oskin]

Hi.

I will give it a try. Although, I do remember that the lock occurs on the
first transaction - so basically there should be nothing to commit yet?

Thanks,
Stas.

-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 21, 2005 9:35 PM
To: Stas Oskin
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Postgres locks table schema? 

"Stas Oskin" <[EMAIL PROTECTED]> writes:
> When running SQL scripts, which change the tables' schema, we sometimes
> experience a lock of these tables' schema. The lock occurs on the first
> command of the script, on the first modified table. When this occurs, no
> further schema modification for this table is possible, until the server
is
> restarted, which is very problematic for a production environment.

Try committing the transaction that performed the schema modification
;-)

regards, tom lane


---(end of broadcast)---
TIP 6: explain analyze is your friend