Julien Viet

well actually it seems that there is a well defined list of parameters for PG : https://www.postgresql.org/docs/9.6/libpq-connect.html Some are transmitted directly to the database like _application_name_, some are interpreted by...

@gavinking I don't disagree with you, I'm saying that some documented parameters are for the client and either the pg client supports them or it does not. So we need...

need to check also what happens with PG when it receives a parameter it does not support

I'm looking at how PGJDBC supports this, and it seems it only supports a fixed size of parameters to be sent at startup: https://github.com/pgjdbc/pgjdbc/blob/473091ad3d60e1cd223b25727fe76d18f3b47f4e/pgjdbc/src/main/java/org/postgresql/core/v3/ConnectionFactoryImpl.java#L352 can you tell which parameters you...

yes we can log them of course

I will try to support more of them like TCP time out, etc... some seem not hard to implement.

does it imply to aggregate SQL statements and parsing them ?

so it does imply interpolation ?

ok that might be fine then, what I don't want is ourselves to replace values into strings

that's open door for security issues