# HG changeset patch
# User Mahlon E. Smith <mahlon@laika.com>
# Date 1520292852 28800
# Node ID 717e89280a2036ae3a3df40cda8bfa9834373f7a
# Parent  e1777929ba15913cb1ddb2c2db4e5d1a5766550e
Update README Timescale example for v0.9.0.

diff -r e1777929ba15 -r 717e89280a20 README.md
--- a/README.md	Tue Feb 20 10:59:26 2018 -0800
+++ b/README.md	Mon Mar 05 15:34:12 2018 -0800
@@ -44,10 +44,10 @@
 Strongly encouraged:  Promote this table to a Timescale "hypertable".
 See [Timescale](http://timescale.com) docs for that, but a quick example
 to partition automatically at weekly boundaries would look something
-like:
+like this, if you're running v0.9.0 or better:
 
 ```sql
-SELECT create_hypertable( 'netdata', 'time', chunk_time_interval => 604800000000 );
+SELECT create_hypertable( 'netdata', 'time', migrate_data => true, chunk_time_interval => '1 week'::interval );
 ```
 
 Timescale also has some great examples and advice for efficient [JSON