pgman v0.4.2

Fixed

• Masked dumps judge a camelCase column name that Postgres folded to
  lower case by its words: an unquoted dateOfBirth is stored
  dateofbirth, which pgman read as one unknown word and kept. On such
  a schema a masked dump kept dates of birth, phone and mobile numbers,
  email addresses, password hashes, bank sort codes and account numbers,
  passport and social security numbers, and special-category columns
  such as sexual orientation. Run pgman masking show again on a schema
  named this way; copies taken with 0.4.0 or 0.4.1 should be deleted
  (pgman copies rm). A phrase such as "account number" now matches
  accountnumber too, and "social security", "building society" and
  "account name" are known.
• pgman masking check, and a masked dump, stop at a masked column a
  validated CHECK constraint names when its masked value may fail it
  (wage > 0 on a nulled NOT NULL wage became 0): the restore stopped
  part-way at the first such row, after the whole dump.
• pgman copies rm names the database it keeps and why; one restored
  through a URL with a password in it said only "invalid configuration:
  password missing".