Skip to content

Commit f66b3f3

Browse files
Add troubleshooting note about partial continuous aggregates (timescale#3164)
Signed-off-by: James Guthrie <[email protected]> Co-authored-by: billy-the-fish <[email protected]>
1 parent 239b03c commit f66b3f3

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

migrate/troubleshooting.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -221,3 +221,29 @@ Timescale instance or "merge" source databases to target schemas.
221221
The `tsdbadmin` database user is the most powerful available on Timescale, but it
222222
is not a true superuser. Review your application for use of superuser privileged
223223
operations and mitigate before migrating.
224+
225+
## Migrate partial continuous aggregates
226+
227+
In order to improve the performance and compatibility of continuous aggregates,
228+
[TimescaleDB v2.7][release-270] replaces _partial_ continuous aggregates with
229+
_finalized_ continuous aggregates.
230+
231+
To test your database for partial continuous aggregates, run the following query:
232+
233+
```SQL
234+
SELECT exists (SELECT 1 FROM timescaledb_information.continuous_aggregates WHERE NOT finalized);
235+
```
236+
237+
If you have partial continuous aggregates in your database, [migrate them][migrate]
238+
from partial to finalized before you migrate your database.
239+
240+
If you accidentally migrate partial continuous aggregates across PostgreSQL
241+
versions, you see the following error when you query any continuous aggregates:
242+
243+
```
244+
ERROR: insufficient data left in message.
245+
```
246+
247+
[migrate]: /migrate/:currentVersion:/live-migration/
248+
[release-270]: /about/:currentVersion:/release-notes/past-releases/#270-2022-05-24
249+

0 commit comments

Comments
 (0)