You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a bit unusual to configure PostgreSQL extensions via environment variables. It would be nice if there were GUCs corresponding to AWS_SHARED_CREDENTIALS_FILE and AWS_CONFIG_FILE.
The text was updated successfully, but these errors were encountered:
To make it more Postgres way, we define 3 s3 related GUCs.
- `pg_parquet.aws_config_file`: an absolute path to the configuration file used by s3 client. Note that when set,
the GUC overrides `AWS_CONFIG_FILE` environment variable. By default the GUC is unset,
- `pg_parquet.aws_shared_credentials_file`: an absolute path to the shared credentials file used by s3 client.
Note that when set, the GUC overrides `AWS_SHARED_CREDENTIALS_FILE` environment variable. By default the GUC is unset,
- `pg_parquet.aws_profile`: the profile name used by s3 client. Note that when set, the GUC overrides `AWS_PROFILE`
environment variable. By default the GUC is unset.
These GUCs can only be set by a superuser. You can easily set these GUCs to use different configurations per session.
You do not need to restart your session to change the config file, shared credentials file or profile name.
Closes#70.
It's a bit unusual to configure PostgreSQL extensions via environment variables. It would be nice if there were GUCs corresponding to AWS_SHARED_CREDENTIALS_FILE and AWS_CONFIG_FILE.
The text was updated successfully, but these errors were encountered: