Re: Using threads in FDW for read-ahead - Mailing list pgsql-interfaces

From Ian Pye
Subject Re: Using threads in FDW for read-ahead
Date
Msg-id CAEVWPAW0Rhc+GS6sA-Hf2rrnF6Ube8qUJM__kZPcEYv7fs2seQ@mail.gmail.com
Whole thread Raw
In response to Using threads in FDW for read-ahead  (Noah Watkins <noahwatkins@gmail.com>)
List pgsql-interfaces
I've done this, but I had to resort to using middleware outside of the FWD.


On Tue, Jun 10, 2014 at 12:10 PM, Noah Watkins <noahwatkins@gmail.com> wrote:
I have created a FDW for a storage backend and it is working well, and now I would like to overlap processing with I/O by performing read-ahead. I started by using a thread to do background I/O and this worked, but problems started to arise when I tried to do predicate filtering in the thread.

In particular, it seems as though `check_stack_depth` is built to assume a single threaded environment (`stack_base_ptr` is global).

I'm wondering if there is a solution to this problem, or if there are examples of overlapping tuple I/O and predicate filtering using non-multithreading techniques?

Thanks,
Noah

pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: Using threads in FDW for read-ahead
Next
From: alpha_one_x86
Date:
Subject: EPOLLPRI CONNECTION_STARTED && host=localhost