Skip site navigation (1) Skip section navigation (2)

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: pgsql-hackers(at)postgresql(dot)org
Subject: Re: type info refactoring
Date: 2010-10-31 21:58:53
Message-ID: 1288562333.5712.13.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On sön, 2010-10-31 at 10:39 -0400, Tom Lane wrote:
> To my mind, the reason we have a distinction between type OID and
> typmod
> is that for most operations, you know the type OID of the result but
> not the typmod.  Trying to force typmod into every API that currently
> works with type OIDs isn't going to alter that, so the net result will
> just be a lot of inefficiency and extra notation to carry around
> "I don't know" markers.

This patch doesn't introduce typmods into places that didn't deal with
them before.  It only replaces function calls and structures that had
separate arguments/fields for type OID and typmod with a single
argument/field.


In response to

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2010-10-31 22:01:11
Subject: Re: type info refactoring
Previous:From: Dimitri FontaineDate: 2010-10-31 21:46:56
Subject: Re: ALTER OBJECT any_name SET SCHEMA name

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group