Add application_name to Connection string when using Postgres Driver

[fracca]

I am using AWS RDS Aurora with Postgres, and they can segment Database load by Application name. I have been able to set this configuration for all my other clients, but I am unable to configure this with CubeJS.

I would like to see either a new ENV variable or a configuration Option or a Default Value if nothing is set.

Looking at the "pg" package documentation, they say that this option is supported. So this change should be pretty simple and quick to implement.

Thanks Team, Keep up the great work.

[igorlukanin]

Looking at the "pg" package documentation, they say that this option is supported.

Could you please share the relevant part? How is it supposed to be configured there?

[fracca]

Hi Igor,

Thanks for getting back to me!

I referenced the following documents:

• [pg.Pool documentation](https://node-postgres.com/apis/pool)

  • "Every field of the config object is entirely optional. The config passed to the pool is also passed to every client instance within the pool when the pool creates that client."

• [pg.Client documentation](https://node-postgres.com/features/connecting#environment-variables)

  • "Every field of the config object is entirely optional. A Client instance will use [environment variables](https://node-postgres.com/features/connecting#environment-variables) for all missing values."

From this, I saw that the application_name parameter is supported as part of the client configuration. Additionally, the documentation indicates that if no value is explicitly set, the client will check for corresponding environment variables.

Based on this, I experimented a bit and found that setting the PGAPPNAME environment variable on the Cube.js API server successfully propagated the application_name in the connection string.

This serves as a workaround for my use case. However, I believe this feature could be more user-friendly if:

1. A configuration option or environment variable specific to Cube.js were implemented to set the application_name value.
2. Alternatively, the documentation could be updated to mention that PGAPPNAME can be used as a workaround to configure application_name.

Let me know what you think, and I’m happy to provide further details or help test any changes!

Thanks again for your time and all the great work the team is doing!

Best regards,
Scott Francis