Re: array_agg() NULL Handling - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: array_agg() NULL Handling
Date
Msg-id AANLkTinQbAptPRsfO8KED2kxpZN=ePNw30AMxLRm14DS@mail.gmail.com
Whole thread Raw
In response to array_agg() NULL Handling  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: array_agg() NULL Handling  ("David E. Wheeler" <david@kineticode.com>)
Re: array_agg() NULL Handling  ("David E. Wheeler" <david@kineticode.com>)
List pgsql-hackers
2010/9/1 David E. Wheeler <david@kineticode.com>:
> The aggregate docs say:
>
>> The first form of aggregate expression invokes the aggregate across all input rows for which the given expression(s)
yieldnon-null values. (Actually, it is up to the aggregate function whether to ignore null values or not — but all the
standardones do.) 
>
> -- http://developer.postgresql.org/pgdocs/postgres/sql-expressions.html#SYNTAX-AGGREGATES
>
> That, however, is not true of array_agg():
>
> try=# CREATE TABLE foo(id int);
> CREATE TABLE
> try=# INSERT INTO foo values(1), (2), (NULL), (3);
> INSERT 0 4
> try=# select array_agg(id) from foo;
>  array_agg
> ──────────────
>  {1,2,NULL,3}
> (1 row)
>
> So are the docs right, or is array_agg() right?

Docs is wrong :) I like current implementation. You can remove a NULLs
from aggregation very simply, but different direction isn't possible

Regards
Pavel Stehule
>
> Best,
>
> David
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Interruptible sleeps (was Re: CommitFest 2009-07: Yay, Kevin! Thanks, reviewers!)
Next
From: Fujii Masao
Date:
Subject: Re: Synchronous replication - patch status inquiry