| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | dilipbalaut(at)gmail(dot)com |
| Cc: | andres(at)anarazel(dot)de, jchampion(at)timescale(dot)com, y(dot)sokolov(at)postgrespro(dot)ru, 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:31:22 |
| Message-ID: | 20220913.163122.1779698487255018129.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sigh..
At Tue, 13 Sep 2022 16:30:06 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> It is possible that the subxip is overrun. We need to expand the array
> somehow. Or assign the array of the size (GetMaxSnapshotXidCount() +
> GetMaxSnapshotSubxidCount()) for takenDuringRecovery snapshots.
And I found that this is already done. What we should is doing the
same thing in snapbuild.
Sorry for the noise..
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-09-13 08:06:03 | Tuples inserted and deleted by the same transaction |
| Previous Message | Kyotaro Horiguchi | 2022-09-13 07:30:06 | Re: Error "initial slot snapshot too large" in create replication slot |