| From: | Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: More parallel-query fun |
| Date: | 2016-07-18 19:00:19 |
| Message-ID: | BLU436-SMTP1692CFB70675B86C6725342F2360@phx.gbl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-06-16 20:14, Tom Lane wrote:
> As of HEAD you can exercise quite a lot of parallel query behavior
> by running the regression tests with these settings applied:
>
> force_parallel_mode = regress
> max_parallel_workers_per_gather = 2 -- this is default at the moment
> min_parallel_relation_size = 0
> parallel_setup_cost = 0
> parallel_tuple_cost = 0
>
> This results in multiple interesting failures, including a core dump
> I saw another previously-unreported problem before getting to the crash:
> Haven't tried to trace that one down yet.
As I expected, I'm unable to reproduce anything of the above - please
correct me if I'm wrong, but it all seems to have been fixed.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-07-18 19:09:07 | Updating our timezone code in the back branches |
| Previous Message | Peter Geoghegan | 2016-07-18 18:33:14 | Re: rethinking dense_alloc (HashJoin) as a memory context |