Add some findings about timescaledb
Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
This commit is contained in:
parent
9971f132fb
commit
8841281325
1 changed files with 9 additions and 0 deletions
|
@ -53,3 +53,12 @@ Finally, you can check that the extension was activated for your database:
|
||||||
::
|
::
|
||||||
$ sudo -u postgres psql <database_name>
|
$ sudo -u postgres psql <database_name>
|
||||||
\dx
|
\dx
|
||||||
|
|
||||||
|
|
||||||
|
Findings
|
||||||
|
--------
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue