Re: Explain output question

From: Patrick Hatcher <PHatcher(at)macys(dot)com>
To: "Tom Lane <tgl" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Explain output question
Date: 2004-10-08 19:21:10
Message-ID: OF367D3994.49A87794-ON88256F27.006A4548-88256F27.006B7FA2@fds.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

thank you. I thought it was correct but just wanted to make sure.

Patrick Hatcher
Macys.Com

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
10/08/04 11:34 AM

To
Patrick Hatcher <PHatcher(at)macys(dot)com>
cc
pgsql-general(at)postgresql(dot)org
Subject
Re: [GENERAL] Explain output question

Patrick Hatcher <PHatcher(at)macys(dot)com> writes:
> Should I be concerned with the merge cond: Merge Cond:
> (("outer".masked_acct_id)::text = "inner"."?column5?")? I have no idea
> what column5 is or the same token the column6 shown later.

You should be able to figure that out by correlating the plan with the
original query. In this case the inner column is clearly
agg.masked_acct_id since there is nothing else that fed.masked_acct_id
would be joined to.

It's annoying that EXPLAIN isn't always able to deliver a reasonable
text representation of values that have bubbled up from a lower plan
level. I've so far not found a good fix, but it's on the to-think-about
list ...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paesold 2004-10-08 19:31:29 Re: Rollback on Error
Previous Message Alvaro Herrera Munoz 2004-10-08 18:57:56 Re: [HACKERS] Rollback on Error