From 68f253d46064ced0bb0634aaa2cc57ee56de2f67 Mon Sep 17 00:00:00 2001
From: "Mahlon E. Smith" <mahlon@martini.nu>
Date: Mon, 5 Mar 2018 15:34:12 -0800
Subject: [PATCH] Update README Timescale example for v0.9.0.

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index f72072f..2e00d4f 100644
--- a/README.md
+++ b/README.md
@@ -44,10 +44,10 @@ functional indexing, etc.  See PostgreSQL documentation for details.
 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