Re: Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"?

h is like custom partitioning. INSERT SAD CAT PICTURE https://gist.github.com/arvenil/b46e927c943fa7495780ea2ae5492e78 Best, Kamil Dziedzic On Thu, Mar 11, 2021 at 10:08 PM Jim Jarvie wrote: > Hi Gunther & List, > > I think I have an extremely similar issue and things point in the s

Re: Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"?

er if you can't lock and just skip it. Best, Saludos, Kamil Dziedzic On Fri, Mar 12, 2021, 17:22 Michael Lewis wrote: > > https://www.postgresql-archive.org/CPU-hogged-by-concurrent-SELECT-FOR-UPDATE-SKIP-LOCKED-td6150480.html > > David Rowley on 20 Aug 2020- > "When upd