| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'Williams, Alex *EXTERN*'" <awilliams(at)teamdrg(dot)com>, Yaser Raja <yrraja(at)gmail(dot)com>, Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Question on Hot Standby in PostgreSQL |
| Date: | 2015-11-25 08:43:10 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B50FEA995@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Alex Williams wrote:
> Concerning these two params below, when using hot_standby_feedback, what would you set them if you
> had the situation where you had queries constantly running on the standby, some quick and some long,
> practically all day/night, everyday?
>
> max_standby_archive_delay (integer)
> max_standby_streaming_delay (integer)
> Should I still keep them as -1 (infinite)?
I'd say set them both to 0.
If you have hot_standby_feedback=on, the primary will not remove any rows still
needed on the standby, so there should never be a need to delay WAL application.
The drawback is that you may get considerable bloat on the primary if many
DELETE/UPDATE operation are going on and queries on the standby take a long time.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mailing Liste | 2015-11-25 11:40:12 | Update postgresql-9.1 fails |
| Previous Message | Albe Laurenz | 2015-11-25 08:37:03 | Re: function nvl(numeric, integer) does not exist |