From: | Alessio Bragadini <alessio(at)albourne(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Changing Column Order (Was Re: MySQL vs PostgreSQL.) |
Date: | 2002-10-14 13:39:37 |
Message-ID: | 1034602777.6205.203.camel@iris |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
On Sat, 2002-10-12 at 11:37, Gavin Sherry wrote:
> I cannot think of any reason why changing column order should be
> implemented in Postgres. Seems like a waste of time/more code bloat for
> something which is strictly asthetic.
>
> Regardless, I do have collegues/clients who ask when such a feature will
> be implemented. Why is this useful?
Has column ordering any effect on the physical tuple disposition? I've
heard discussions about keeping fixed-size fields at the beginning of
the tuple and similar.
Sorry for the lame question. :-)
--
Alessio F. Bragadini alessio(at)albourne(dot)com
APL Financial Services http://village.albourne.com
Nicosia, Cyprus phone: +357-22-755750
"It is more complicated than you think"
-- The Eighth Networking Truth from RFC 1925
From | Date | Subject | |
---|---|---|---|
Next Message | Diogo Biazus | 2002-10-14 13:52:51 | PostgreSQL Benchmarks |
Previous Message | Adam Witney | 2002-10-14 13:14:23 | Re: Recover db |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-14 13:53:27 | Re: droped out precise time calculations in src/interfaces/libpq/fe-connect.c |
Previous Message | Denis A Ustimenko | 2002-10-14 06:40:43 | Re: droped out precise time calculations in src/interfaces/libpq/fe-connect.c |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-14 14:11:05 | Re: [GENERAL] Prepared statement performance... |
Previous Message | Peter Kovacs | 2002-10-14 12:03:20 | Re: [GENERAL] Prepared statement performance... |