Andrew Dunstan <andrew(at)dunslane(dot)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
In response to
pgsql-patches by date
|Next:||From: Kris Jurka||Date: 2008-01-29 05:09:28|
|Subject: Re: Proposed patch: synchronized_scanning GUC variable|
|Previous:||From: Ron Mayer||Date: 2008-01-29 00:13:09|
|Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable|