On Sat, Nov 26, 2022 at 19:50 PM Amit Kapila wrote:
> On Fri, Nov 25, 2022 at 5:30 PM Ashutosh Bapat
> wrote:
> >
> > Hi Hou,
> > Thanks for the patch. With a simple condition, we can eliminate the
> > need to queueing snapshot change in the current transaction and then
> > applying it. Saves
On Fri, Nov 25, 2022 at 5:30 PM Ashutosh Bapat
wrote:
>
> Hi Hou,
> Thanks for the patch. With a simple condition, we can eliminate the
> need to queueing snapshot change in the current transaction and then
> applying it. Saves some memory and computation. This looks useful.
>
> When the queue
Hi Hou,
Thanks for the patch. With a simple condition, we can eliminate the
need to queueing snapshot change in the current transaction and then
applying it. Saves some memory and computation. This looks useful.
When the queue snapshot change is processed in
ReorderBufferProcessTXN(), we call
Hi,
When doing some other related work, I noticed that when decoding the COMMIT
record via SnapBuildCommitTxn()-> SnapBuildDistributeNewCatalogSnapshot() we
will add a new snapshot to all transactions including the one being
decoded(just committed one).
But since we've already done required
