diff --git a/docs/datanommer_datagrepper/pg_timescaledb.rst b/docs/datanommer_datagrepper/pg_timescaledb.rst
index 4cfec50..9b281f5 100644
--- a/docs/datanommer_datagrepper/pg_timescaledb.rst
+++ b/docs/datanommer_datagrepper/pg_timescaledb.rst
@@ -62,3 +62,12 @@ After converting the `messages` table to use timescaledb, we've realized that
 timescaledb uses table partitioning as well.
 This leads to the same issue with the foreign key constraints that we have seen
 in the plain partitioning approach we took.
+
+
+Open questions
+--------------
+
+* How will upgrading the postgresql version with the timescaledb plugin look like?
+
+It looks like the timescaledb folks are involved enough in postgresql itself that
+we think things will work, but we have not had on-hands experience with it.