| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Toomas Kristin <toomas(dot)kristin(at)gmail(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Conflict with recovery on PG version 11.6 |
| Date: | 2020-06-20 12:03:09 |
| Message-ID: | fab3d72fcdda3f7b3fd67cca4b8cbc8f72f6faad.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, 2020-06-20 at 06:51 +0300, Toomas Kristin wrote:
> Thank you for help. hot_standby_feedback did what I expected (no lag on replication
> and no session termination) and case is closed. Only it is foggy for me how it can
> be when no logs about vacuuming from that time window when session is active on standby host.
Perhaps heap only tuple chain pruning.
Have you got "n_tup_hot_upd" > 0 somewhere in "pg_stat_user_tables"?
Then any reader can "micro-vacuum" blocks with such tuples.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2020-06-20 16:28:52 | Re: i am getting issue as FATAL: password authentication failed for user ' postgres' tried |
| Previous Message | Paul Förster | 2020-06-20 07:04:47 | Re: Netapp SnapCenter |