Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

PostgreSQL setup - database encoding

  • Filter
  • Time
  • Show
Clear All
new posts

  • PostgreSQL setup - database encoding


    I originally set up PostgreSQL 8.2 for use with Mirth 1.5. At the time, I just took the default encoding (SQL_ASCII) when Postgres created the database.

    Subsequently when doing maintenance with PgAdmin, I see a "tip" that says I should use something with more bits, like UTF-8.

    Should I switch? If so, can I do that by dumping the database with format=P (plain ascii) and then creating the new database with encoding <whatever you told me> and restoring from the SQL file I created?

    If I should switch, should I do this before or after I upgrade to Mirth 1.6?