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 A58A5D1B965; Fri, 31 Oct 2003 19:52:16 +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 63886-09; Fri, 31 Oct 2003 15:51:46 -0400 (AST) Received: from candle.pha.pa.us (unknown [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 10019D1B979; Fri, 31 Oct 2003 15:51:23 -0400 (AST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h9VJn0J04943; Fri, 31 Oct 2003 14:49:00 -0500 (EST) From: Bruce Momjian Message-Id: <200310311949.h9VJn0J04943@candle.pha.pa.us> Subject: Re: Annotated release notes In-Reply-To: <3FA1F902.7000407@joeconway.com> To: Joe Conway Date: Fri, 31 Oct 2003 14:49:00 -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: 200310/52 X-Sequence-Number: 2072 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 = '{}' > ); What had me really confused was the first release item: Allow polymorphic SQL functions (Joe) How does an SQL function query the data types passed to it? Once I saw that I thought I didn't underestand what polymorphic functions were. Right now we have: Allow user defined aggregates to use polymorphic functions (Joe) bjm ?? Allow polymorphic user defined aggregates (Joe) These seem like duplicates. Are polymorphic functions currently most useful for aggregates? Why would someone want polymorphic aggregates? That is what I was hoping for. -- 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