Node 14.0.0 - pg does not response
See original GitHub issueRunning a postgres locally
import { Pool } from 'pg';
const pool = new Pool({})
describe('check connexion', () => {
it('should select 1', async () => {
const result = await pg.query('SELECT 1 as hey');
expect(result.rows[0]).toEqual({ hey: 1 });
});
afterAll(() => pg.end());
});
Fails with current node 14.0.0 Works on node 12.16.2.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Node.JS Heroku Postgres Connection not working
seems to work fine. Doing a bit of research, it seems there are/have been some issues with v14 and pg Node 14.0. 0...
Read more >pg - npm
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF...
Read more >Node.JS Heroku Postgres Connection not working-postgresql
Doing a bit of research, it seems there are/have been some issues with v14 and pg Node 14.0.0 - pg does not response...
Read more >Monitoring Node.js - IBM
The Instana Node.js collector is an npm package that you add to the ... On Cloud Foundry, a configuration is not required at...
Read more >Previous Releases - Node.js
Version Date V8 npm NODE_MODULE_VERSION
Node.js 19.3.0 2022‑12‑14 10.8.168.21 9.2.0 111 Downloads C...
Node.js 19.2.0 2022‑11‑29 10.8.168.20 8.19.3 111 Downloads C...
Node.js 19.1.0 2022‑11‑14 10.7.193.20 8.19.3...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is fixed in pg@8.0.3. If you see this happening
pg>=8.0.3
please feel free to re-open this issue.Oh gosh. I lost 3 days on this problem because I thought it was related to networks in docker containers. Solution worked.