From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <hackers(at)postgreSQL(dot)org> |
Subject: | Re: Fix for select sum(2+2)... |
Date: | 1998-01-15 03:57:21 |
Message-ID: | 34BD8920.4C4BC803@sable.krasnoyarsk.su |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> I have decided the whole qry_aggs is bad. It is bad becuase it makes
> multiple copies of Aggreg, and both copies must be processed by any
> changes by rewrite and optimizer. I am removing the field
> Query->qry_aggs, and replacing it with a function that will called when
> creating the Agg which spins through the Plan target list and returns a
> linked list of Agg*. Much cleaner, and I can remove much of the special
> qry_aggs handling I added to get other Agg stuff to work.
>
> Also, this relates to the SubLink change. I am now going to recommend
> not having a separate Sublink pointer list field in Query, but adding a
> function that will return a list of valid Sublink entries in from
> qry->qual, or maybe even qry->targetlist.
Agreed. This will also simplify readfuncs.c
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim B. Mikheev | 1998-01-15 04:01:52 | Re: [HACKERS] Just a small thing for 6.3 ... |
Previous Message | Thomas G. Lockhart | 1998-01-15 03:54:15 | Re: [HACKERS] Re: [QUESTIONS] trouble grouping rows |