X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 49516D1B507; Mon, 10 Nov 2003 22:27:44 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 00355-02; Mon, 10 Nov 2003 18:27:14 -0400 (AST) Received: from candle.pha.pa.us (unknown [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 5E23DD1B504; Mon, 10 Nov 2003 18:27:10 -0400 (AST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id hAAMQI422144; Mon, 10 Nov 2003 17:26:18 -0500 (EST) From: Bruce Momjian Message-Id: <200311102226.hAAMQI422144@candle.pha.pa.us> Subject: Re: Annotated release notes In-Reply-To: <3FA1F902.7000407@joeconway.com> To: Joe Conway Date: Mon, 10 Nov 2003 17:26:18 -0500 (EST) Cc: Tatsuo Ishii , peter_e@gmx.net, neilc@samurai.com, chriskl@familyhealth.com.au, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org, PostgreSQL-documentation X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/22 X-Sequence-Number: 2099 OK, release notes updated to: Allow polymorphic PL/pgSQL functions (Tom, Joe) Allow polymorphic SQL functions (Joe) Allow functions to accept arbitrary data types for input, and return arbitrary types. --------------------------------------------------------------------------- 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@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073