Re: Arrays of Complex Types - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Arrays of Complex Types
Date
Msg-id 20070403020143.GA8484@alvh.no-ip.org
Whole thread Raw
In response to Re: Arrays of Complex Types  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Arrays of Complex Types  (David Fetter <david@fetter.org>)
List pgsql-hackers
Bruce Momjian wrote:
>
> Your patch has been added to the PostgreSQL unapplied patches list at:
>
>     http://momjian.postgresql.org/cgi-bin/pgpatches
>
> It will be applied as soon as one of the PostgreSQL committers reviews
> and approves it.
>

So, hum, what happened to the idea of creating the array types only on
demand?

>
>
> David Fetter wrote:
> > On Fri, Mar 30, 2007 at 05:08:42PM -0400, Tom Lane wrote:
> > > David Fetter <david@fetter.org> writes:
> > > > After several rounds of patches, it appears that it might be easier to
> > > > create a new typtype entry, which I'll tentatively call 'a' because it
> > > > seems a little fragile and a lot inelegant and hard to maintain to
> > > > have typtype='c' and typrelid=InvalidOid mean, "this is an array of
> > > > complex types."
> > >
> > > Uh, wouldn't it be typtype = 'c' and typelem != 0 ?
> >
> > Right.  The attached patch passes the current regression tests and at
> > least to a "smoke test" level does what it's supposed to do.  I'd
> > really like to help refactor the whole array system to use 'a', tho.
> >
> > Cheers,


--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Feature thought: idle in transaction timeout
Next
From: Andrew Dunstan
Date:
Subject: Re: Feature thought: idle in transaction timeout