Re: Patch for removng unused targets - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Patch for removng unused targets
Date
Msg-id 14993.1354552292@sss.pgh.pa.us
Whole thread Raw
In response to Re: Patch for removng unused targets  ("Etsuro Fujita" <fujita.etsuro@lab.ntt.co.jp>)
Responses Re: Patch for removng unused targets  ("Etsuro Fujita" <fujita.etsuro@lab.ntt.co.jp>)
Re: Patch for removng unused targets  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
"Etsuro Fujita" <fujita.etsuro@lab.ntt.co.jp> writes:
> Sorry for the delay.  I've reviewed the patch.  It was applied
> successfully, and it worked well for tests I did including the example
> you showed.  I think it's worth the work, but I'm not sure you go
> about it in the right way.  (I feel the patch decreases code
> readability more than it gives an advantage.)

One thought here is that I don't particularly like adding a field like
"resorderbyonly" to TargetEntry in the first place.  That makes this
optimization the business of the parser, which it should not be; and
furthermore makes it incumbent on the rewriter, as well as anything else
that manipulates parsetrees, to maintain the flag correctly while
rearranging queries.  It would be better if this were strictly the
business of the planner.

But having said that, I'm wondering (without having read the patch)
why you need anything more than the existing "resjunk" field.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Markus Wanner
Date:
Subject: Re: Review: Extra Daemons / bgworker
Next
From: "Kevin Grittner"
Date:
Subject: Re: Materialized views WIP patch