| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, jeff(dot)janes(at)gmail(dot)com, frank(dot)gagnepain(at)intm(dot)fr, pgsql-bugs(at)lists(dot)postgresql(dot)org, Mark Wong <mark(at)2ndquadrant(dot)com> |
| Subject: | Re: BUG #16476: pgp_sym_encrypt_bytea with compress-level=6 : Wrong key or corrupt data |
| Date: | 2020-07-22 14:39:43 |
| Message-ID: | 7555.1595428783@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Wed, Jul 22, 2020 at 05:45:54PM +0900, Kyotaro Horiguchi wrote:
>> Might be help if the test prints the orignal and the decrypted bytes?
> And turning the buildfarm completely red? No, thanks. Those random
> strings are also too long to be analyzed easily.
Is there a reason why the test string has to be non-constant?
The current form of the test would be fine if things were working,
but it offers absolutely zero chance of diagnosing problems.
For starters, it'd be nice to know whether the encrypt or the
decrypt side is going wrong.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tutiluren | 2020-07-22 15:17:27 | Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. |
| Previous Message | PG Bug reporting form | 2020-07-22 11:22:05 | BUG #16552: In Setup wizard, Locale "Spanish, Spain" present twice |