pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Merlin Moncure <mmoncure@gmail.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Trevor Talbot <quension@gmail.com>
Cc: Roberts, Jon <Jon.Roberts@asurion.com>
Cc: Kris Jurka <books@ejurka.com>
Cc: Jonah H. Harris <jonah.harris@gmail.com>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: pgsql performance <pgsql-performance@postgresql.org>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: function body actors (was: viewing source code)
Date: Fri, 21 Dec 2007 09:13:32 -0500
Message-ID: <b42b73150712210613s1cc85c76p47e6a4bb36257fbe@mail.gmail.com> (raw)
In-Reply-To: <162867790712210018m68117783y791da209a4a97448@mail.gmail.com>
References: <b42b73150712202109u26d05d01q4f1b8be8d29f763c@mail.gmail.com>
	<26811.1198215605@sss.pgh.pa.us>
	<b42b73150712202306v58b9f301kbea90bf8e150ddfc@mail.gmail.com>
	<162867790712210018m68117783y791da209a4a97448@mail.gmail.com>

On Dec 21, 2007 3:18 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> I have similar patch and it works. There is two isues:
>
> * we missing column in pg_proc about state (not all procedures are
> obfuscated), I solved it for plpgsl with using probin.

I was hoping to avoid making any catalog or other changes to support
encryption specifically.  Maybe your patch stands on its own
merits...I missed the original discussion.  Do you think the code you
wrote can be adapted to do other things besides encryption?

> * decrypt is expensive on language handler level. Every session have
> to do it again and again, better decrypt in system cache or somewhere
> there.

Doesn't bother me in the least...and caching unencrypted data is
scary.  Also, aes256 is pretty fast for what it gives you and function
bodies are normally short.  The real issue as I see it is where to
keep the key.  How did you handle that?

merlin



view thread (8+ messages)  latest in thread

Message-ID: <b42b73150712210613s1cc85c76p47e6a4bb36257fbe@mail.gmail.com>
Permalink:  ../b42b73150712210613s1cc85c76p47e6a4bb36257fbe@mail.gmail.com/
Also on:    postgresql.org/message-id/b42b73150712210613s1cc85c76p47e6a4bb36257fbe@mail.gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: mmoncure@gmail.com, pavel.stehule@gmail.com, tgl@sss.pgh.pa.us, alvherre@commandprompt.com, jd@commandprompt.com, quension@gmail.com, Jon.Roberts@asurion.com, books@ejurka.com, jonah.harris@gmail.com, wmoran@collaborativefusion.com, pgsql-hackers@postgresql.org
  Subject: Re: function body actors (was: viewing source code)
  In-Reply-To: <b42b73150712210613s1cc85c76p47e6a4bb36257fbe@mail.gmail.com>
  References: <b42b73150712202109u26d05d01q4f1b8be8d29f763c@mail.gmail.com> <26811.1198215605@sss.pgh.pa.us> <b42b73150712202306v58b9f301kbea90bf8e150ddfc@mail.gmail.com> <162867790712210018m68117783y791da209a4a97448@mail.gmail.com> <b42b73150712210613s1cc85c76p47e6a4bb36257fbe@mail.gmail.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