From: | Ian Pye <ianpye(at)gmail(dot)com> |
---|---|
To: | Noah Watkins <noahwatkins(at)gmail(dot)com> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Using threads in FDW for read-ahead |
Date: | 2014-06-10 19:23:10 |
Message-ID: | CAEVWPAW0Rhc+GS6sA-Hf2rrnF6Ube8qUJM__kZPcEYv7fs2seQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | alpha_one_x86 | 2014-06-18 10:56:59 | EPOLLPRI CONNECTION_STARTED && host=localhost |
Previous Message | Tom Lane | 2014-06-10 19:21:01 | Re: Using threads in FDW for read-ahead |