Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error When Connecting to Redshift #443

Closed
valeeum opened this issue Dec 21, 2022 · 2 comments
Closed

Error When Connecting to Redshift #443

valeeum opened this issue Dec 21, 2022 · 2 comments

Comments

@valeeum
Copy link

valeeum commented Dec 21, 2022

I get the following error when I try to connect to redshift using the createPool method. Does this library work with the older postgres specification that redshift uses (8.0.2)?

column "typarray" does not exist in pg_type

Expected Behavior

Should connect successfully.

Current Behavior

Connection errors out with: "column "typarray" does not exist in pg_type"

Steps to Reproduce

Try to connect using createPool method:

          const pool = await slonik.createPool(
            "postgresql://user:password@someredshifturl.us-east-1.redshift.amazonaws.com:5439/somedefaultdb",
          );

Logs

err: { "type": "DatabaseError", "message": "column \"typarray\" does not exist in pg_type", "stack": error: column "typarray" does not exist in pg_type at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:287:98) at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29) at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38) at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42) at Socket.emit (events.js:400:28) at Socket.emit (domain.js:475:12) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at Socket.Readable.push (internal/streams/readable.js:206:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23)

@valeeum valeeum added the bug label Dec 21, 2022
@gajus
Copy link
Owner

gajus commented Sep 26, 2023

It appears not. Not something I would actively prioritize working on since I have no exposure to Redshift. PRs welcome.

@gajus gajus closed this as completed Sep 26, 2023
@gajus gajus added enhancement and removed bug labels Sep 26, 2023
@gajus
Copy link
Owner

gajus commented Sep 26, 2023

Removing "bug" since it is not an officially supported backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants