Re: Confusing EXPLAIN output in case of inherited tables

From: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Confusing EXPLAIN output in case of inherited tables
Date: 2012-01-31 03:56:47
Message-ID: CAFjFpRf-Tzo=eO_EFn07ZmsRrmqi2X06Pv6G8hg0JaHAzeB5iQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I don't believe that the problem has anything to do with the names of

> other tables that might happen to exist in the database. It's a matter
> of what RTE names/aliases are exposed for variable references in
> different parts of the query.
>
>
Names of other tables come into picture when we schema qualify the fake
aliases in the generated query. See examples in first post.

> regards, tom lane
>

--
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-01-31 04:18:31 Re: pg_dump -s dumps data?!
Previous Message Josh Berkus 2012-01-31 03:07:52 Re: [GENERAL] Why extract( ... from timestamp ) is not immutable?