From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jon Lapham <lapham(at)extracta(dot)com(dot)br> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Problem with a rule on upgrade to v7.1.1 |
Date: | 2001-05-11 19:59:40 |
Message-ID: | 6727.989611180@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jon Lapham <lapham(at)extracta(dot)com(dot)br> writes:
> PS: (Talking *way* above my head now) Would be possible to have
> EXPLAIN flag this type of problem? Remember, the EXPLAIN output for
> 7.1RC1 and 7.1.1 were identical.
Yeah, because EXPLAIN doesn't show the individual qual clauses attached
to each plan node. EXPLAIN VERBOSE does ... but it's, um, too verbose
for most people.
I've speculated to myself about designing some intermediate level of
EXPLAIN display that would show things like qual clauses and indexscan
conditions in a readable fashion (unlike EXPLAIN VERBOSE). It could use
the ruleutils.c code to produce the output, so there's not that much
coding involved, just some tasteful selection of exactly what details to
show and how to format the output. But I haven't gotten around to
actually doing anything ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Blasby | 2001-05-11 20:00:50 | Rtree on custom data types; type conversion stops index use. |
Previous Message | Jon Lapham | 2001-05-11 19:46:58 | Re: Problem with a rule on upgrade to v7.1.1 |