Re: Using threads in FDW for read-ahead
От
Ian Pye
Тема
Re: Using threads in FDW for read-ahead
Дата
Msg-id
CAEVWPAW0Rhc+GS6sA-Hf2rrnF6Ube8qUJM__kZPcEYv7fs2seQ@mail.gmail.com
Ответ на
Using threads in FDW for read-ahead (Noah Watkins)
Список
Дерево обсуждения
Using threads in FDW for read-ahead Noah Watkins <noahwatkins@gmail.com>
Re: Using threads in FDW for read-ahead Tom Lane <tgl@sss.pgh.pa.us>
Re: Using threads in FDW for read-ahead Ian Pye <ianpye@gmail.com>
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 по дате отправления
