| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martha Chronopoulou <mchron(at)aueb(dot)gr> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: implementing another hash join... |
| Date: | 2004-10-13 22:28:48 |
| Message-ID: | 18789.1097706528@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martha Chronopoulou <mchron(at)aueb(dot)gr> writes:
> Im new to postgres and I'm about to implement the algorithm "double
> pipelined hash join". I've started using SPI functions but soon I
> realised that I 'm not at the right way (am I?).
Not even close. You need to be implementing new executor node types
(see backend/executor) and teaching the planner about the properties
of this join method. SPI is at a completely different level of
abstraction ...
> Is there a way that I'm not obliged to change code of the optimizer of
> postgres
Nope. The set of join types it knows about is pretty much hard-wired.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2004-10-14 00:49:03 | Re: First set of OSDL Shared Mem scalability results, some |
| Previous Message | Tom Lane | 2004-10-13 21:56:07 | pgsql: Fix breakage in hashjoin from recent backpatch of left-join bug |