Re: additional contrib test suites
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: David Steele <david@pgmasters.net>,
pgsql-hackers <pgsql-hackers@postgresql.org>,
Thomas Munro <thomas.munro@enterprisedb.com>
Date: 2017-09-15T20:15:04Z
Lists: pgsql-hackers
I wrote: > Peter Eisentraut <peter.eisentraut@2ndquadrant.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
Commits
-
Remove contrib/chkpass
- 5d3cad564729 11.0 landed
-
doc: Clarify pg_inherits description
- 0b554e4e63a4 11.0 cited