It seems that Postgres (9.5 at least) limits the length of channels for NOTIFY and LISTEN:
# LISTEN "pg/tables/TagNotificationTriggers/tag/_org/1/JSON Test/battery/1/lifetimeWh";
NOTICE: identifier "pg/tables/TagNotificationTriggers/tag/_org/1/JSON Test/battery/1/lifetimeWh"
will be truncated to "pg/tables/TagNotificationTriggers/tag/_org/1/JSON Test/battery/"
Finding out about this was a bit of a rude awakening. I just complained on the Postgres mailing list that no channel length limit is mentioned in their documentation. I don't know if graphql-postgres-subscriptions has a way to catch the NOTICE from postgres, but at the very least it would probably be helpful for graphql-postgres-subscriptions print a warning to the console if a topic is longer than 63 characters.
It seems that Postgres (9.5 at least) limits the length of channels for
NOTIFYandLISTEN:Finding out about this was a bit of a rude awakening. I just complained on the Postgres mailing list that no channel length limit is mentioned in their documentation. I don't know if
graphql-postgres-subscriptionshas a way to catch theNOTICEfrom postgres, but at the very least it would probably be helpful forgraphql-postgres-subscriptionsprint a warning to the console if a topic is longer than 63 characters.