| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Should we remove vacuum_defer_cleanup_age? |
| Date: | 2023-04-14 18:08:56 |
| Message-ID: | CAM-w4HMDy=vrbE7KEQmaRi-Dtg0jKh3jxa4z6+7cBA11K4T6ew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 14 Apr 2023 at 13:15, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Fri, 2023-04-14 at 18:43 +0200, Alvaro Herrera wrote:
> > On 2023-Apr-14, Greg Stark wrote:
> > > I assume people would use hot_standby_feedback if they have streaming
> > > replication.
> >
> > Yes, either that or a replication slot.
>
> A replication slot doesn't do anything against snapshot conflicts,
> which is what we are discussing here. Or are we not?
They're related -- the replication slot holds the feedback xmin so
that if your standby disconnects it can reconnect later and not have
lost data in the meantime. At least I think that's what I think it
does -- I don't know if I'm just assuming that, but xmin is indeed in
pg_replication_slots.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-04-14 18:38:44 | Re: refactoring relation extension and BufferAlloc(), faster COPY |
| Previous Message | Tom Lane | 2023-04-14 17:57:15 | Re: daitch_mokotoff module |