Workers using pg library unable to parse Postgres database DSN

Apr 2, 21:23 UTC
Resolved - This incident has been resolved. Any impacted developers should update their npm dependencies to use [email protected] or newer, [email protected] or newer. (In the rare case when an application depends on pg-connection-string directly, this package should also be updated to version 2.6.4 or newer).

Apr 2, 17:26 UTC
Identified - We have identified an incompatibility issue with the latest 2.6.3 version of the pg-connection-string library used by the node-postgres library and the Node.js polyfill used by the Workers runtime. This may also impact other libraries that require the Node.js "url" package.

This will result in a runtime error related to the URL constructor with the text URL is not a constructor.

A fix to the way this is polyfilled is in-progress. In the meantime, users can choose to downgrade to pg-connection-string version 2.6.2 and pg version 8.11.3, which does not import the "url" package.

Apr 2, 17:14 UTC
Update - We are continuing to investigate this issue.

Apr 2, 16:56 UTC
Investigating - New Workers deployed using URI to parse a database (Data Search Name) DSN are failing to parse. We are currently investigating the root cause. This is also impacting newly deployed Hyperdrives ability to connect to databases.


This is a companion discussion topic for the original entry at https://www.cloudflarestatus.com/incidents/5kb1f8jjdjnl

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.