Prevent exact `timestamptz` mismatches in node-postgres by preserving text

PostgreSQL stores timestamps with microsecond resolution, but JavaScript Date only carries milliseconds. With node-postgres's default parser, a value such as: becomes: The final 456 microseconds disappear. This is harmless for display-oriented code, but it can break equality checks, cursor construction, audit comparisons, and read-modify-write paths that expect the database value to round-trip…