Timeline for Working memory on the connection string for postgres instance
Current License: CC BY-SA 4.0
5 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 8, 2019 at 13:31 | comment | added | jjanes | Ok, -c might be libpq specific. Can you tell what library within nodejs you are using to connect? There seems to be several. Abstracting the connection logic to a routine which can do housekeeping commands before handing the connection back is probably a better design anyway. Rather than stuffing all the logic into a connection string which then gets fired from multiple parts of the code. | |
May 8, 2019 at 10:20 | comment | added | bmvr | Hello, I've tried it, didn't work. I had to set work_mem = 'xxMB' before when I opened the connection, this was not what I wanted but well.. it works. | |
May 8, 2019 at 10:19 | vote | accept | bmvr | ||
May 8, 2019 at 10:19 | |||||
May 7, 2019 at 18:09 | comment | added | user1822 |
I don't think a connection string for Node.js supports the -c parameter
|
|
May 7, 2019 at 17:46 | history | answered | jjanes | CC BY-SA 4.0 |