On 06/27/2018 09:55 AM, Moreno Andreo wrote:
> Il 22/06/2018 19:56, Adrian Klaver ha scritto:
>> On 06/22/2018 09:50 AM, Moreno Andreo wrote:
>>> Il 22/06/2018 15:18, Adrian Klaver ha scritto:
>>
>>
>> I am at a loss now. The only thing I can think of is that data itself
>> is actually corrupted. Maybe some sort of language encoding/collation
>> issue. Just not sure how to test that at the moment.
>
> Actually, I tried it in a bunch of other fields with varying data types
> and everything went fine.
> I don't know if it's as you say and I mismatched keys (and I need
> another pair of glasses) or something else. Just hoping (but being
> confident) it won't happen again.
You might try emailing the pgcrypto author
https://www.postgresql.org/docs/10/static/pgcrypto.html#id-1.11.7.35.11
In the source code I noticed that there are many:
px_debug('Some text')
that map to:
{PXE_PGP_CORRUPT_DATA, "Wrong key or corrupt data"}.
I tried running with messages set to DEBUG to see if I could get at the
more specific messages. That did not work, so you might ask the author
if there is a way to get at them.
>
> Now trying to speed up a little some queries involving SELECTing among
> these encrypted fields, if I'm stuck I'll open a new thread.
>
> Thanks,
> Moreno.-
>
>>
>>
--
Adrian Klaver
adrian.klaver@aklaver.com
