On Thu, Oct 1, 2026 at 9:18 AM Andrey Borodin <[email protected]> wrote: > > On 1 Oct 2026, at 13:28, Zsolt Parragi <[email protected]> wrote: > > > > Maybe we should open a bug report to pg_lake about this? Even if we > > allow for this here, the documentation still requires es_snapshot to > > be set. > > It's the cost of breaking old pg_lake users and possible unknown buggy users > against cost of extra runtime check for all others. > > I don't have personal preferences in this choice. But I suspect that project > policy is that Postgres works. Without much surprises.
One of the pg_lake maintainers here; so the basic issue is that we didn't populate the es_snapshot field in the Estate, so just setting that to the active current snapshot before calling ExecCheckIndexConstraints() is the fix? TL;DR; this is only an 18/19 issue, or it needs backported all the way down? Thanks,. David
