| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel Full Hash Join |
| Date: | 2020-11-04 22:33:58 |
| Message-ID: | CAAKRu_aXXrArQ9zR3GmGPj8AjReihCJSV_-TyfiFpY6AP8bW6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I've attached a patch with the corrections I mentioned upthread.
I've gone ahead and run pgindent, though, I can't say that I'm very
happy with the result.
I'm still not quite happy with the name
BarrierArriveAndDetachExceptLast(). It's so literal. As you said, there
probably isn't a nice name for this concept, since it is a function with
the purpose of terminating parallelism.
Regards,
Melanie (Microsoft)
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Support-Parallel-FOJ-and-ROJ.patch | text/x-patch | 26.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-11-04 23:07:37 | Re: PANIC: could not fsync file "pg_multixact/..." since commit dee663f7843 |
| Previous Message | Tomas Vondra | 2020-11-04 22:25:22 | Re: Fix brin_form_tuple to properly detoast data |