| From: | Venkata Balaji N <nag1010(at)gmail(dot)com> |
|---|---|
| To: | Jordi <jmaillists(at)promani(dot)be> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Shipping big WAL archives to hot standby |
| Date: | 2016-04-10 08:05:51 |
| Message-ID: | CAEyp7J8rnbdJxP=O_rOWxp1bU8GrEf80+tov-QLiaEmtQ9drOw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> What would be the effect of suddenly introducing a 1-2 GB of WAL archives
> to the WAL restore folder on the slave? Would there be a big performance
> effect on the incoming queries to the slave? Would the slave be available
> for queries while the WAL logs are restored into the DB?
>
If the Queries are running on slave whilst WAL archives are being applied,
there is a bright chance that, queries would encounter a conflict with the
recovery and would eventually get cancelled. You can see messages in the
PostgreSQL logfiles. The recommended approach would be to apply WALs when
queries are being executed on slave.
Regards,
Venkata B N
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bannert Matthias | 2016-04-10 09:06:32 | Re: max_stack_depth problem though query is substantially smaller |
| Previous Message | David G. Johnston | 2016-04-10 07:30:26 | Re: Bypassing NULL elements in row_to_json function |