| From: | Vik Fearing <vik(at)2ndquadrant(dot)fr> |
|---|---|
| To: | Chris Travers <chris(dot)travers(at)gmail(dot)com>, Scott Mead <scottm(at)openscg(dot)com> |
| Cc: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Uber migrated from Postgres to MySQL |
| Date: | 2016-07-27 17:08:42 |
| Message-ID: | c8166989-0a43-20e2-b604-e6d286f6a2d8@2ndquadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 27/07/16 18:54, Chris Travers wrote:
> Another one I think they obliquely referred to (in the subtle problems
> section) was the fact that if you have longer-running queries on the
> replica with a lot of updates, you can get funny auto-vacuum-induced
> errors (writes from autovacuum on the master can interrupt queries on
> the slave). BTW if there is interest in what could be done for that,
> something which allows autovacuum to decide how long to wait before
> cleaning up dead tuples would be a great enhancement.
You mean something like hot_standby_feedback?
https://www.postgresql.org/docs/current/static/runtime-config-replication.html#GUC-HOT-STANDBY-FEEDBACK
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Fournier | 2016-07-27 17:54:25 | Re: Uber migrated from Postgres to MySQL |
| Previous Message | Bruce Momjian | 2016-07-27 17:04:10 | Re: Uber migrated from Postgres to MySQL |