| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Noah Misch <noah(at)leadboat(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Subject: | Re: Intermittent buildfarm failures on wrasse |
| Date: | 2022-04-15 21:51:26 |
| Message-ID: | 1802041.1650059486@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On April 15, 2022 2:14:47 PM EDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I could use some help filling in the XXX comments, because it's far
>> from clear to me *why* walsenders need this to happen.
> If you want to commit before: The reason is that walsenders use their xmin to represent the xmin of standbys when using hot_standby_feedback. Since we're only transmitting global horizons up from standbys, it has to influence globally (and it would be hard to represent per db horizons anyway).
Got it. I rewrote the comments and pushed. Noah, it should be safe
to turn wrasse back on.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sahil Harpal | 2022-04-15 22:36:27 | GSOC-2022 | Improve pgarchives proposal review |
| Previous Message | Ilaria Battiston | 2022-04-15 20:40:42 | Re: [GSOC-22] Proposal Review |