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

Re: More missing docs (aggs)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-docs(at)postgresql(dot)org
Subject: Re: More missing docs (aggs)
Date: 2006-12-11 17:38:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Uh, why do you think that's significant?  The stype is whatever you
>> need to use.

> Right, but do you have two stypes for a multi-col, a single stype, or a 
> composite stype?  The docs don't say and it's not obvious.

There is only one transition state variable, as I should think would be
reasonably obvious from the wording:

    An aggregate function is made from one or two ordinary functions: a
    state transition function sfunc, and an optional final calculation
    function ffunc. These are used as follows:

    sfunc( internal-state, next-data-values ) ---> next-internal-state
    ffunc( internal-state ) ---> aggregate-value

    PostgreSQL creates a temporary variable of data type stype to hold
    the current internal state of the aggregate. At each input row, the
    aggregate argument value(s) are calculated and the state transition
    function is invoked with the current state value and the new
    argument value(s) to calculate a new internal state value.

Whether the state value is a composite type or not is up to the
aggregate author.  There aren't any examples of using a composite type
in the docs, but there are examples of using an array as stype, so
I would hope that our users are bright enough to think of composites
when they need one.

			regards, tom lane

In response to


pgsql-docs by date

Next:From: Josh BerkusDate: 2006-12-11 17:44:39
Subject: Re: More missing docs (aggs)
Previous:From: Josh BerkusDate: 2006-12-11 17:29:07
Subject: Re: More missing docs (aggs)

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