There is a bug in pool when connection cannot be established at pool start #478

Activity

1. langpavel commented on Apr 20, 2024

   

   langpavel

   on Apr 20, 2024

   ContributorAuthor

   More actions

   I think this is somewhere in DeferredAccessStack, but I have no proof, except this:

   deno-server-1           | Insert successful
   deno-server-1           | ERROR ConnectionRefused: Connection refused (os error 111)
   deno-server-1           |     at async Object.connect (ext:deno_net/01_net.js:587:55)
   deno-server-1           |     at async Connection.#openConnection (https://deno.land/x/postgres@v0.19.3/connection/connection.ts:266:18)
   deno-server-1           |     at async Connection.#startup (https://deno.land/x/postgres@v0.19.3/connection/connection.ts:342:7)
   deno-server-1           |     at async Connection.startup (https://deno.land/x/postgres@v0.19.3/connection/connection.ts:494:11)
   deno-server-1           |     at async PoolClient.connect (https://deno.land/x/postgres@v0.19.3/client.ts:233:7)
   deno-server-1           |     at async DeferredAccessStack.pop (https://deno.land/x/postgres@v0.19.3/utils/deferred.ts:115:7)
   deno-server-1           |     at async _custom_ (file:///home/deno/fake-device/_custom_.ts:51:26)
   deno-server-1           |     at async Promise.all (index 2)
   deno-server-1           |     at async file:///home/deno/main.ts:17:3 {
   deno-server-1           |   name: "ConnectionRefused",
   deno-server-1           |   code: "ECONNREFUSED"
   deno-server-1           | }
   
2. langpavel commented on Apr 20, 2024

   

   langpavel

   on Apr 20, 2024

   ContributorAuthor

   More actions

   This will only happen when deno service is starterd before postgres.
3. langpavel commented on Apr 20, 2024

   

   langpavel

   on Apr 20, 2024

   ContributorAuthor

   More actions

   Don't know if related, but I'm using lazy mode.