3669 docs rfc add new live sync guide to the migration section #3671
Conversation
|
Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-3669-docs-rfc-add-new-live-sync-guide-to-the-migration-section |
migrate/live-sync.md
Outdated
| @@ -0,0 +1,282 @@ | |||
| --- | |||
| title: Live sync | |||
There was a problem hiding this comment.
I suggest we add Postgres as suffix as its targeted for only Postgres
There was a problem hiding this comment.
Gone the whole hog: Livesync from Postgres to Timescale Cloud
migrate/live-sync.md
Outdated
|
|
||
| You use the live-sync Docker image to synchronize changes in real-time from a PostgreSQL database | ||
| instance to a $SERVICE_LONG. You run live-sync continuously, turning PostgreSQL into a primary database | ||
| with a $SERVICE_LONG as a logical replica. This enables you to leverage $CLOUD_LONG’s real-time analytics |
There was a problem hiding this comment.
Can we also add a mention that user gets to to choose to replicate all or some of their data with choosen tables.
There was a problem hiding this comment.
@VineethReddy02 @billy-the-fish We should also highlight the fact that this is not intended for migration, but just to keep synching data for analytics. We expect the primary to be running all the time.
Though it could be a potential migration path, the UX is not ready for that yet.
migrate/page-index/page-index.js
Outdated
| @@ -15,6 +15,11 @@ module.exports = [ | |||
| href: "live-migration", | |||
| excerpt: "Migrate a large database with low downtime", | |||
| }, | |||
| { | |||
| title: "Live sync", | |||
There was a problem hiding this comment.
Same "Postgres Livesync", for naming consistency can be name as one word livesync?
There was a problem hiding this comment.
As above.
Livesync is now a proper noun for this feature. Maybe we can change the name of the image to livesync as well?
migrate/live-sync.md
Outdated
| </Procedure> | ||
|
|
||
|
|
||
| ## Limitations |
There was a problem hiding this comment.
At least for now, I would prefer to keep the limitation just after the intro. Because, the user must understand that they need to migrate schema using pg_dump/restore
| <Highlight type="important"> | ||
| Avoid using connection strings that route through connection poolers like PgBouncer or similar tools. The live-migration tool requires a direct connection to the database to function properly. | ||
| </Highlight> | ||
| Avoid using connection strings that route through connection poolers like PgBouncer or similar tools. This tool requires a direct connection to the database to function properly. |
There was a problem hiding this comment.
This is an important point which I feel must be highlighted. Otherwise users tend to ignore and think using connection pooler is always better and end up in trouble.
migrate/live-sync.md
Outdated
|
|
||
| You use the live-sync Docker image to synchronize changes in real-time from a PostgreSQL database | ||
| instance to a $SERVICE_LONG. You run live-sync continuously, turning PostgreSQL into a primary database | ||
| with a $SERVICE_LONG as a logical replica. This enables you to leverage $CLOUD_LONG’s real-time analytics |
There was a problem hiding this comment.
@VineethReddy02 @billy-the-fish We should also highlight the fact that this is not intended for migration, but just to keep synching data for analytics. We expect the primary to be running all the time.
Though it could be a potential migration path, the UX is not ready for that yet.
Co-authored-by: Arunprasad Rajkumar <[email protected]> Signed-off-by: Iain Cox <[email protected]>
billy-the-fish
deleted the
3669-docs-rfc-add-new-live-sync-guide-to-the-migration-section
branch
No description provided.