From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Konstantin Izmailov <pgfizm(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_attribute.attnum - wrong column ordinal? |
Date: | 2009-12-05 14:46:34 |
Message-ID: | 1260024394.20505.0.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On tor, 2009-12-03 at 10:09 -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Should we recast the attributes and columns views in information_schema?
> > I notice they still use attnum.
>
> I'd vote against it, at least until we have something better than a
> row_number solution. That would create another huge performance penalty
> on views that are already ungodly slow.
Should be easy to test the performance impact of this, since the limit
for columns per table is 1600.
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2009-12-05 14:54:58 | Re: Array comparison & prefix search |
Previous Message | marco di antonio | 2009-12-05 13:19:21 | Help with starting portable version of postgresql |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-12-05 15:39:13 | Re: PostgreSQL Release Support Policy |
Previous Message | Tim Bunce | 2009-12-05 13:56:00 | Re: First feature patch for plperl - draft [PATCH] |