| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: t_self as system column |
| Date: | 2010-07-06 21:32:39 |
| Message-ID: | 14669.1278451959@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Jul 6, 2010 at 5:18 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> Why wouldn't it be feasible?
> Just because it might be too much to do all at once.
My thought is that the hardest part of this is going to be making sure
that every "column index" usage in the code is properly categorized as
to whether it's physical, logical, or identifier index. If we try to
divide the problem into sub-patches, that will probably just increase
the amount of effort because all that code will have to be looked at
twice.
Think of it as Polya's paradox in action.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-07-06 21:37:31 | pgsql: Add note that using PL/Python 2 and 3 in the same session will |
| Previous Message | Robert Haas | 2010-07-06 21:24:21 | Re: t_self as system column |