Re: type info refactoring

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: type info refactoring
Date: 2010-10-31 22:04:24
Message-ID: 1288562664.5712.18.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On sön, 2010-10-31 at 13:01 -0400, Tom Lane wrote:
> But I'm still wondering whether it's smart to try to promote all of
> this fundamentally-auxiliary information to first-class status. It's
> really unclear to me that that will end up being a net win either
> conceptually or notationally.

Fair enough, but this patch arose from the discussion that the collation
patch had a lot of hunks that just changed (typeid, typmod) to (typeid,
typmod, collation) and that that could be isolated by collecting those
into a common data structure. We can abandon this line of thought and
I'll go back to my original project, but I thought others who are
thinking about improving typmods could also benefit from this work.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2010-10-31 22:09:23 Re: ALTER OBJECT any_name SET SCHEMA name
Previous Message Robert Haas 2010-10-31 22:02:55 Re: ALTER OBJECT any_name SET SCHEMA name