Parsing Error for Data Types w/ OID Outside of int4 Range

[e-rich18]

Values that have a data type OID that is outside of the int4 range (i.e. > 2147483647), do not get parsed correctly. This seems especially true for array types, but it could effect any data type with such an OID.

Steps to reproduce:

1. Create a custom data type in your postgres database (i.e. CREATE TYPE ...) that has an OID outside of the int4 range (I don't know exactly how to accomplish that since it doesn't seem to be deterministic so it may take some trial and error)
2. Run a select query using Client.query that includes a column having that data type.

Expected Behavior
Column parses according to parsing rules for that data type (e.g. an array is parsed into a JS array)

Actual Behavior
The column is set to a plain string (e.g. '{element,element}' for an array).

Since OIDs are not typically set through manual intervention, this needs to be fixed in the library.

[charmander]

node-postgres/packages/pg-protocol/src/parser.ts

Line 264 in 249182e

const dataTypeID = this.reader.int32()

Even though https://www.postgresql.org/docs/current/protocol-message-formats.html specifies Int32, I guess this needs uint32?

[gus-civitas]

node-postgres/packages/pg-protocol/src/parser.ts

Line 264 in 249182e

const dataTypeID = this.reader.int32()

Even though https://www.postgresql.org/docs/current/protocol-message-formats.html specifies Int32, I guess this needs uint32?

The same is probably true for the readers implementation for int16

[charmander]

@gus-civitas In which context? Definitely not all of them.