| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | andres(at)anarazel(dot)de |
| Cc: | jchampion(at)timescale(dot)com, y(dot)sokolov(at)postgrespro(dot)ru, dilipbalaut(at)gmail(dot)com, rjuju123(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Error "initial slot snapshot too large" in create replication slot |
| Date: | 2022-09-13 07:15:34 |
| Message-ID: | 20220913.161534.1763577367544098635.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Tue, 13 Sep 2022 15:45:07 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> At Mon, 12 Sep 2022 14:51:56 -0700, Andres Freund <andres(at)anarazel(dot)de> wrote in
> > This sees a tad misleading - the previous snapshot wasn't borken, right?
>
> I saw it kind of broken that ->xip contains sub transactions. But I
> didn't meant it's broken by "correct". Is "proper" suitable there?
No. It's not broken if it is takenDuringRecovery. So this flag can be
used to notify that xip can be oversized.
I realized that rbtxn_is_known_subxact is not reliable. I'm
redirecting to oversized xip. Pleas wait for a while.
regareds.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2022-09-13 07:20:01 | Re: Removed unused param isSlice of function transformAssignmentSubscripts |
| Previous Message | Michael Paquier | 2022-09-13 07:13:20 | Re: pg_basebackup's --gzip switch misbehaves |