Heikki Linnakangas <hlinnakan...@vmware.com> writes: > On 10/03/2014 07:08 AM, Kouhei Kaigai wrote: >> What is the best way to solve the problem?
> How about creating a separate ResourceOwner for these buffer pins, and > doing a wholesale ResourceOwnerRelease() on it when you're done? That's a thought. Another point is that if you can release the buffer pins in reverse order of acquisition, the existing ResourceOwner code works just fine. I have a larger question though: how is it useful to transfer raw contents of shared buffers to a GPU in the first place? Surely you're not going to be putting tasks like tuple visibility verification into the GPU. So it seems like this whole thread is based on a dubious architectural assumption. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers