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

Re: Annotated release notes

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, peter_e(at)gmx(dot)net,neilc(at)samurai(dot)com, chriskl(at)familyhealth(dot)com(dot)au, tgl(at)sss(dot)pgh(dot)pa(dot)us,pgsql-hackers(at)postgresql(dot)org,PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Annotated release notes
Date: 2003-11-10 22:26:18
Message-ID: 200311102226.hAAMQI422144@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-docspgsql-hackers
OK, release notes updated to:

<listitem><para>Allow polymorphic PL/pgSQL functions (Tom, Joe)</para></listitem>
<listitem><para>Allow polymorphic SQL functions (Joe)</para>
   <para>
    Allow functions to accept arbitrary data types for input, and return arbitrary types.
   </para>
   </listitem>


---------------------------------------------------------------------------

Joe Conway wrote:
> Bruce Momjian wrote:
> > 	http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-7-4
> > 
> > I need people to check this and help me with the items marked 'bjm'.  I
> > am confused about the proper text for those sections.
> 
>  > Allow polymorphic SQL functions (Joe)
>  > bjm ??
> 
> What isn't clear about this? Should/can we refer to related sections of 
> the manual?
> http://developer.postgresql.org/docs/postgres/xfunc-sql.html#AEN28722
> http://developer.postgresql.org/docs/postgres/extend-type-system.html#EXTEND-TYPES-POLYMORPHIC
> 
>  > Allow user defined aggregates to use polymorphic functions (Joe)
>  > bjm ??
> 
> Same question. From this url:
> http://developer.postgresql.org/docs/postgres/xaggr.html
> see this paragraph:
> 
>   Aggregate functions may use polymorphic state transition functions or 
> final functions, so that the same functions can be used to implement 
> multiple aggregates. See Section 33.2.1  for an explanation of 
> polymorphic functions. Going a step further, the aggregate function 
> itself may be specified with a polymorphic base type and state type, 
> allowing a single aggregate definition to serve for multiple input data 
> types. Here is an example of a polymorphic aggregate:
> 
> CREATE AGGREGATE array_accum (
>      sfunc = array_append,
>      basetype = anyelement,
>      stype = anyarray,
>      initcond = '{}'
> );
> 
> Joe
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-docs by date

Next:From: Bruce MomjianDate: 2003-11-10 23:48:07
Subject: Re: Runtime Basics
Previous:From: Peter EisentrautDate: 2003-11-10 18:47:34
Subject: Re:

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2003-11-10 23:02:32
Subject: Re: [PATCHES] initdb in C
Previous:From: Bruce MomjianDate: 2003-11-10 22:22:55
Subject: Re: Experimental patch for inter-page delay in VACUUM

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