Comment on ListenBrainz moves to TimescaleDBparentComments−akulkarni6yTimescaleDB offers a number of backup and restore options, including wal-e (WAL-based), pg_dump & pg_restore:https://docs.timescale.com/latest/using-timescaledb/backupThere are hundreds of thousands of TimescaleDB databases in production so this is generally not an issue.−brightball6ySeemed like an odd issue to be outstanding. I assume if this was a real issue it would be a much bigger story.−k-rus6yCorrect, the issue is due to confusing notices printed during pg_dump as it uses COPY TO underneath.
Comments
TimescaleDB offers a number of backup and restore options, including wal-e (WAL-based), pg_dump & pg_restore:
https://docs.timescale.com/latest/using-timescaledb/backup
There are hundreds of thousands of TimescaleDB databases in production so this is generally not an issue.
Seemed like an odd issue to be outstanding. I assume if this was a real issue it would be a much bigger story.
Correct, the issue is due to confusing notices printed during pg_dump as it uses COPY TO underneath.