pg-promise with AWS Lambda and RDS proxy

[abozhilov]

Hi everyone,
I need some clarifications about the connection pool.
Imagine the following scenario:

AWS Lambda with pg-promise -> RDS Proxy -> Postgres

In the lambda function pgp.end() is never called and I want to maintain a connection pool in the lambda function and warm instances to utilise it. That's good, but RDS Proxy itself also manages a connection pool and it's a bit unclear for me what happens in pg-promise if a warm lambda instance tries to reuse a connection which is closed by RDS Proxy?

LLMs suggest to use a retry strategy when I query the DB in case of transient error, but that doesn't seem right to me as my pg-promise connection pool could be e.g. 10, then to make sure the code works I will need maximum 10 retries.

Upon acquiring a connection from the pg-promise pool do you check if the connection is still alive or I will receive an error when I try to query the DB?

Thanks!

[vitaly-t]

Questions related to AWS were discussed too many times at this point, which I am not willing to reiterate here again. Just research the subject against the underlying driver. This library doesn't really add anything on top of that in terms of connectivity.