Logical replication tips
Learn how to optimize for logical replication
The following tips are based on actual customer data migrations to Neon using logical replication:
-
If you are replicating a large dataset to Neon, check whether your indexes exceed 20 GB in size. To estimate the total size of your indexes, run the following query on the source database:
If the size of your indexes exceeds 20 GB, contact Neon Support to request an increase in the fixed disk size for your Neon compute. A larger disk size will help prevent
no space left on device
errors. Neon Support may also make additional modifications to your Neon compute to prepare for replicating a large dataset. -
Initial data copying during logical replication can significantly increase the load on both the publisher and subscriber. For large data migrations, consider increasing compute resources (CPU and RAM) for the initial copy. On Neon, you can do this by enabling autoscaling and selecting a larger maximum compute size. The publisher (source database instance) typically experiences higher load, as it serves other requests while the subscriber only receives replicated data.
-
For large datasets, avoid creating indexes when setting up the schema on the destination database (subscriber) to reduce the initial data load time. Indexes can be added back after the data copy is complete.
-
If you encounter replication timeout errors, consider increasing
wal_sender_timeout
on the publisher andwal_receiver_timeout
on the subscriber to a higher value, such as 5 minutes (default is 1 minute). On Neon, adjusting these settings requires assistance from Neon Support. -
To minimize storage consumption during data replication to Neon, reduce your history retention setting. For example, set it to 1 hour or 0 during the initial copy, and restore it to the desired value afterward.
If you have tips you would like to share, please let us know via the Feedback form in the Neon Console or our feedback channel on Discord.