> 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. Best regards, Andrey Borodin.
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Dean Rasheed
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Andrey Borodin
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Dean Rasheed
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Zsolt Parragi
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Andrey Borodin
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Dean Rasheed
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Zsolt Parragi
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Dean Rasheed
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Andrey Borodin
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Zsolt Parragi
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Andrey Borodin
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... David Christensen
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... Zsolt Parragi
- Re: SSI: ON CONFLICT DO SELECT takes no predicate lock o... David Christensen
