|
| Why SQLEXEC always create NEW connection in POSTGRES ? |
| Iniciado por Mygocoogs, 17,abr. 2020 06:07 - 2 respuestas |
| |
| | | |
|
| |
| Publicado el 17,abril 2020 - 06:07 |
Hi there,
I'm using WD to connect to Postgres db.
I noticed that each new SQLEXEC in new window always created new connection with new client port.
This is strange because I called SQLCONNECT only ONCE at the beginning thus I expect WD to keep using same connection.
I found out about this when I checked using PG_STAT_ACTIVITY in postgres and saw many connections from same user and app. And this has resulted in consuming the available connection in database thus reducing total number users can connect.
Any chance that I can change this in WD programming to tell WD to not open new connection once SQLCONNECT is established ?
Many thanks in advance for your valuable advices.
Adiy |
| |
| |
| | | |
|
| | |
| |
Miembro registrado
50 mensajes |
|
| Publicado el 17,abril 2020 - 18:50 |
| Are you using SQLClose after you finish each query ? |
| |
| |
| | | |
|
| | |
| |
| Publicado el 18,abril 2020 - 14:11 |
Hi,
Thanks for the advice.
I checked SQLCLOSE() but it was not the cause.
Apparently the cause is the setting of Window control.
It was solved by unticking setting Window -> Detail ->Independent HyperFileSQL context. |
| |
| |
| | | |
|
| | | | |
| | |
|