add caching for topic content db calls (Postgres only)
authorJustin Wind <justin.wind+git@gmail.com>
Thu, 5 Aug 2021 22:11:21 +0000 (15:11 -0700)
committerJustin Wind <justin.wind+git@gmail.com>
Fri, 6 Aug 2021 00:17:29 +0000 (17:17 -0700)
Cache topicContentGetById responses, to avoid many large-payload db
calls when updating subscribers.  Currently only enabled for Postgres,
which uses the LISTEN/NOTIFY mechanism on topic updates to invalidate
cache entries, ensuring data consistency.


No differences found