From: Alessio Bragadini <alessio@albourne.com>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Changing Column Order (Was Re: MySQL vs PostgreSQL.)
Date: 14 Oct 2002 16:39:37 +0300
Message-ID: <1034602777.6205.203.camel@iris> (raw)
In-Reply-To: <Pine.LNX.4.21.0210121833480.26079-100000@linuxworld.com.au>
References: <Pine.LNX.4.21.0210121833480.26079-100000@linuxworld.com.au>
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@albourne.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alessio@albourne.com
Subject: Re: Changing Column Order (Was Re: MySQL vs PostgreSQL.)
In-Reply-To: <1034602777.6205.203.camel@iris>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox