On Thu, Jan 22, 2015 at 10:30 AM, Amit Kapila <amit.kapil...@gmail.com> wrote: > > On Thu, Jan 22, 2015 at 6:37 AM, Kouhei Kaigai <kai...@ak.jp.nec.com> wrote: > > > > (Please point out me if my understanding is incorrect.) > > > > What happen if dynamic background worker process tries to reference temporary > > tables? Because buffer of temporary table blocks are allocated on private > > address space, its recent status is not visible to other process unless it is > > not flushed to the storage every time. > > > > Do we need to prohibit create_parallelscan_paths() to generate a path when > > target relation is temporary one? > > > > Yes, we need to prohibit parallel scans on temporary relations. Will fix. >
Here is the latest patch which fixes reported issues and supported
Prepared Statements and Explain Statement for parallel sequential
scan.
The main purpose is to get the feedback if possible on overall
structure/design of code before I goahead.
Note -
a. it is still based on parallel-mode-v1 [1] patch of Robert.
b. based on CommitId - fd496129 [on top of this commit, apply
Robert's patch and then the attached patch]
c. just build and tested on Windows, my linux box has some
problem, will fix that soon and verify this on linux as well.
[1]
http://www.postgresql.org/message-id/ca+tgmozduk4k3xhbxc9vm-82khourezdvqwtfglhwsd2r2a...@mail.gmail.com
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
parallel_seqscan_v6.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
