Re: WIP: plpgsql source code obfuscation - Mailing list pgsql-patches

From Tom Lane
Subject Re: WIP: plpgsql source code obfuscation
Date
Msg-id 11005.1201573783@sss.pgh.pa.us
Whole thread Raw
In response to Re: WIP: plpgsql source code obfuscation  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-patches
Andrew Dunstan <andrew@dunslane.net> writes:
> using this example, it seems to me that if we dump the encrypted/encoded
> source and restore into another database with a different encoding, the
> decoded/decrypted source will still be in the old database encoding,
> i.e. not valid in the new database encoding. We've just gone around
> closing doors like this.

Ah, right, I hadn't thought about that, but it would be a hazard.

            regards, tom lane

pgsql-patches by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Proposed patch: synchronized_scanning GUC variable
Next
From: Kris Jurka
Date:
Subject: Re: Proposed patch: synchronized_scanning GUC variable