From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | David Steele <david(at)pgmasters(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Subject: | Re: additional contrib test suites |
Date: | 2017-09-15 20:15:04 |
Message-ID: | 2041.1505506504@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> So, we have one failure for chkpass on OpenBSD, because OpenBSD crypt()
>> doesn't support the traditional two-character salt format.
>> Option:
>> - Use the resultmap features to make this an expected failure on OpenBSD.
>> - Fix the module to work on OpenBSD. This would involve making a
>> platform-specific modification to use whatever advanced salt format they
>> want.
>> - Replace the entire module with something that does not depend on crypt().
> Or (4) drop the module's regression test again.
Noting that mandrill is showing yet a different failure, one that I think
is inherent to chkpass:
CREATE TABLE test (i int, p chkpass);
INSERT INTO test VALUES (1, 'hello'), (2, 'goodbye');
+ WARNING: type chkpass has unstable input conversion for "hello"
+ LINE 1: INSERT INTO test VALUES (1, 'hello'), (2, 'goodbye');
+ ^
+ WARNING: type chkpass has unstable input conversion for "goodbye"
+ LINE 1: INSERT INTO test VALUES (1, 'hello'), (2, 'goodbye');
+ ^
I'm starting to think that (4) might be the best avenue. Or we could
consider
(5) drop contrib/chkpass altogether, on the grounds that it's too badly
designed, and too obsolete crypto-wise, to be useful or supportable.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2017-09-15 20:17:52 | Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers) |
Previous Message | Tom Lane | 2017-09-15 20:07:33 | Re: COMMIT TRIGGERs, take n, implemented with CONSTRAINT TRIGGERS |