When running postgres in a production environment the documentation recommends using table sharding https://tyk.io/docs/api-management/tyk-pump/#sharding

I could not get this to work in my kubernetes tyk environment so I opened a ticket with support and they told me the following variables need to be set:

TYK_DB_STORAGE_MAIN_TABLESHARDING=true
TYK_DB_ENABLEAGGREGATELOOKUPS=true

... plus some extra variables for tyk-pump but they also added the following:
"Please make sure that in the Dashboard, TYK_DB_STORAGE_ANALYTICS_TYPE and TYK_DB_STORAGE_LOGS_TYPE are unset . This is because the configuration above will work if you haven't set these 2 config ."

This presents a problem in the helm chart as TYK_DB_STORAGE_ANALYTICS_TYPE is hard coded to postgres when the helm value global.storageType is postgres, which of course it is in my case. I manually patched the deployment resource and this does in fact fix the original issue.

I understand that requiring TYK_DB_STORAGE_ANALYTICS_TYPE to be unset would probably be considered a work around and in some future tyk-dashboard version this would not be required but until then I would love to be able to optionally unset this variable.