persistent-postgresql 2.13.0.1 test failures with persistent-test 2.13.0.3

Failures:

  src/PersistentTest.hs:80:9:
  1) persistent.SafeToRemove.DudeWeirdColumns can insert and get
       uncaught exception: SqlError
       SqlError {sqlState = "23502", sqlExecStatus = FatalError, sqlErrorMsg = "null value in column \"bar\" of relation \"DudeWeirdColumns\" violates not-null constraint", sqlErrorDetail = "Failing row contains (2, hello, null, null).", sqlErrorHint = ""}

  To rerun use: --match "/persistent/SafeToRemove/DudeWeirdColumns/can insert and get/"

  src/PersistentTest.hs:86:9:
  2) persistent.SafeToRemove.DudeWeirdColumns can putMany
       uncaught exception: FormatError
       FormatError {fmtMessage = "6 single '?' characters, but 2 parameters", fmtQuery = "INSERT INTO \"DudeWeirdColumns\"(\"name\", \"foo\", \"bar\") VALUES (?, ?, ?), (?, ?, ?) ON CONFLICT (\"name\") DO UPDATE SET \"name\"=EXCLUDED.\"name\", \"foo\"=EXCLUDED.\"foo\", \"bar\"=EXCLUDED.\"bar\"", fmtParams = ["goodbyue","hello"]}

  To rerun use: --match "/persistent/SafeToRemove/DudeWeirdColumns/can putMany/"

Start with the failing tests in src/PersistentTest.hs at lines 80 and 86. Rerun the two cases using the provided --match patterns, then inspect the persistent-postgresql test setup and generated SQL. Done means both DudeWeirdColumns tests pass without the reported SqlError or FormatError.