Re: explain plan difference - Mailing list pgsql-general

From Tom Lane
Subject Re: explain plan difference
Date
Msg-id 14145.1572840079@sss.pgh.pa.us
Whole thread Raw
In response to explain plan difference  (Steve Baldwin <steve.baldwin@gmail.com>)
Responses Re: explain plan difference  (Steve Baldwin <steve.baldwin@gmail.com>)
List pgsql-general
Steve Baldwin <steve.baldwin@gmail.com> writes:
> I guess the difference doesn't have a huge bearing (as far as I can tell)
> on the result, but it just seems odd that the inner-most 'Output' step
> outputs the entire row in the case of the copy and only the required field
> in the case of the original table. What triggers that behaviour?

The plan with the full output row is actually slightly cheaper, or at
least so the planner thinks, because it saves a projection step.
I imagine the reason you're not getting that with the original table
is that there are some dropped column(s) in the original table, forcing
the projection to be done to get rid of them.

            regards, tom lane



pgsql-general by date:

Previous
From: Steve Baldwin
Date:
Subject: explain plan difference
Next
From: Steve Baldwin
Date:
Subject: Re: explain plan difference