[SQL] Encrypt data type LO

[Alberto Piña]

Hi fellows, I need to encrypt fields of data type
LO (LO is included in the contrib section of PostgreSQL) and I don’t know
if pgcrypto is the way to do that or there is another way.  If anyone
knows the answer of my problem or know an alternative way to do this,
I’ll appreciate you can share this with me.

Regards.

 

Ing. Carlos Alberto Piña Uribe

Consultoría y Desarrollo

KEBIR Infraestructura Tecnológica

[EMAIL PROTECTED]

 

[SQL] Explicitly rolling back transaction from within a C-Language function

[Mark Dilger]

Hello,

I have a transactional system built on top of
BerkeleyDB which I would like to call from within
Postgres through a C-Language function.  The behavior
of the function will be read-only.  Even so, the
BerkeleyDB-based system's transaction will sometimes
fail.  What I would like to do is propogate that
transactional failure into the Postgres transaction
that called the C-Language function.  Is this
possible?

To clarify what I think I want:  I would like the
C-Language function to return an error condition to
Postgres that will cause the current Postgres
transaction to abort.  I do not know how to do this.

I am not particularly worried about needing to
rollback the BerkeleyDB transaction when the Postgres
transaction fails, because the BerkeleyDB transaction
was read-only anyway, and there are no updates to roll
back.  However, I might want to do this in the future
so information on this subject is also welcome.

Thank you for any help,

mark



__ 
Do you Yahoo!? 
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com 

---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match

Re: [SQL] Explicitly rolling back transaction from within a C-Language function

[Michael Fuhr]

On Wed, Nov 24, 2004 at 11:23:30AM -0800, Mark Dilger wrote:

> To clarify what I think I want:  I would like the
> C-Language function to return an error condition to
> Postgres that will cause the current Postgres
> transaction to abort.  I do not know how to do this.

See the "Reporting Errors Within the Server" documentation:

http://www.postgresql.org/docs/7.4/static/error-message-reporting.html

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org