| From: | Mladen Gogala <gogala(dot)mladen(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Reindex "locked" standby database |
| Date: | 2021-12-15 03:52:36 |
| Message-ID: | 75898e59-aa59-0293-1398-b9d1bcf70a3b@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/14/21 22:37, Michael Paquier wrote:
> You are referring to the startup process that replays WAL, right?
> Without having an idea about the type of workload your primary and/or
> standbys are facing, as well as an idea of the configuration you are
> using on both (hot_standby_feedback for one), I have no direct idea,
> but that could be a conflict caused by a concurrent vacuum.
Hi Michael,
I am preparing for a standby deployment. I don't have a standby yet and,
therefore, I don't have any standby problems. Would it be advisable to
turn vacuum off on the standby? Applying WAL will also, in theory,
populate the statistics which is also held in the database blocks.
Regards
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martín Fernández | 2021-12-15 04:10:45 | Re: Reindex "locked" standby database |
| Previous Message | Michael Paquier | 2021-12-15 03:37:35 | Re: Reindex "locked" standby database |