Re: (PATCH) Adding CORRESPONDING to Set Operations

From: Kerem Kat <keremkat(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thom Brown <thom(at)linux(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: (PATCH) Adding CORRESPONDING to Set Operations
Date: 2011-11-14 14:09:31
Message-ID: CAJZSWkUHRWbQ4htoL4WP9xzHwjGMpa1mjphz9KZrSS4Y7e3C7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 14, 2011 at 15:32, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Kerem Kat <keremkat(at)gmail(dot)com> writes:
>> Corresponding is currently implemented in the parse/analyze phase. If
>> it were to be implemented in the planning phase, explain output would
>> likely be as you expect it to be.
>
> It's already been pointed out to you that doing this at parse time is
> unacceptable, because of the implications for reverse-listing of rules
> (views).
>
>                        regards, tom lane
>

I am well aware of that thank you.

Regards,

Kerem KAT

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-11-14 14:24:17 Re: Working with git repo tagged versions
Previous Message Tom Lane 2011-11-14 13:32:47 Re: (PATCH) Adding CORRESPONDING to Set Operations