As discussed on chatroom, there is no documentation for the possibility to use key=val fields that are passed directly to libpq to allow custom fields without the need to use LIBPQ internal environment variables. It can be quite useful in many cases, especially certificate authentication against the database. https://github.com/mwild1/luadbi/blob/4fc37754128320a2a4254fa76dd3735215c39f73/dbd/postgresql/connection.c#L91
Adding to this, it also takes a DB URI in the form postgresql://user@host:port/db?param=uriencoded_value
As discussed on chatroom, there is no documentation for the possibility to use key=val fields that are passed directly to libpq to allow custom fields without the need to use LIBPQ internal environment variables. It can be quite useful in many cases, especially certificate authentication against the database. https://github.com/mwild1/luadbi/blob/4fc37754128320a2a4254fa76dd3735215c39f73/dbd/postgresql/connection.c#L91
Adding to this, it also takes a DB URI in the form postgresql://user@host:port/db?param=uriencoded_value