Postgres server restart maybe required if the variables do not appear on the custom dimensions.
Ideally what should happen is that the MP sends the information about the new dimension to zookeeper, which in turn sends it to the edge-postgres-server component which is responsible for sending the command that adds an extra column in the relevant fact table in the postgresql database.
We have seen issues where the zookeeper notification does not reach the postgres-server component thus preventing the additional column from getting created. A restart of the postgres-server component typically resolves the issue because during a restart postgres-server reads all information relevant to AX from zookeeper.
We have an open jira for the notification getting lost issue but as this is a design issue, the bug will not get fixed until the redesign of the AX component becomes available in private cloud with one of the next releases.
LinkedIn
Twitter
