On Thu, Feb 12, 2015 at 1:51 AM, Robert Haas <[email protected]> wrote: > > > I think we may want a dedicated parallel-safe property for functions > rather than piggybacking on provolatile, but that will probably also > be changeable via ALTER FUNCTION, and stored rules won't get > miraculously updated. So this definitely can't be something we figure > out at parse-time ... it's got to be determined later. But at the > moment I see no way to do that without an extra pass over the whole > rewritten query tree. :-( >
If we have to go this way, then isn't it better to evaluate the same when we are trying to create parallel path (something like in the parallel_seq scan patch - create_parallelscan_paths())? With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
