Mike Freedman

Add explicit PostgreSQL support/instructions

1

Should provide instructions how to test vanilla PostgreSQL tables, rather than TimescaleDB hypertgables.

Chunk sizing in best practices should refer to `shared_buffers`, as discussed in https://github.com/timescale/docs.timescale.com-content/issues/294

``` Time intervals: The current release of TimescaleDB enables both the manual and automated adaption of its time intervals. With manually-set intervals, users should specify a chunk_time_interval when creating their...

Users can report a segfault, but then often struggle to generate a core dump, and sometimes don't have binaries installed with DEBUG symbols to enable useful stack traces. Would be...

[Change] Warning not to use TimescaleDB builds from Postgres repo (apache version)

1

Users are told to go to the Postgres repo's to get postgres, but they might also install TimescaleDB from there. But those versions are Apache only and not built by...

We should add a section to both Timescale Cloud and Forge describing support for HA (on Cloud -> Pro Plans; on Forge -> all services are HA using disaggregated storage...

The "scaling out" section referenced in this tip (https://docs.timescale.com/getting-started/scaling-out) no longer exists. Should refer to new/different section around multi-node TimescaleDB. Location: https://docs.timescale.com/latest/getting-started/creating-hypertables 

[Update] Instructions for migrating data from existing PG table

1

Our docs provides isntructions for migrating from the same database, but appears to have been written prior to the support for `migrate_data` in a hypertable. Specifically, it suggests creating a...

If you are creating a cagg on a hypertable with a lot of existing data, current best practices are not to create a policy back to beginning of time, but...