I have a Postgresql 9.1 database that is being hosted by Heroku. It currently has a read-only "follower". I need to truncate several large tables (over 100GB) of data and reloads them. Is the read-only follower going to cause an additional overhead to this operation? Should I drop the follower and recreate it after the process is complete?
Postgresql – Write performance of Postgresql 9.1 with read-only slave
herokupostgresqlpostgresql-9.1replication
Related Question
- PostgreSQL – Clustered Index vs. Table Ordered by Column
- MySQL Replication – How to Improve Performance Reading Relay Logs
- PostgreSQL – How to Compress Database
- Postgresql – Postgres Upsert Performance Considerations (millions of rows/hour)
- PostgreSQL: Disk usage and hardware utilization and performance
- Amazon RDS Performance – Why Do RDS Read IOPS Drop After a Certain Period?
Best Answer
Truncate should be a logical operation that should not be too bad disk I/O-wise. I would not expect a lot of problems there.