Greg Stark <[EMAIL PROTECTED]> writes:
> Incidentally, "HashAggregate"?! Based on the earlier discussion on this I
> would have expected that line to read "Materialize"
It's using a grouped aggregation node to implement a UNIQUE filter, so
that it can replace the "WHERE foo IN (subselect)" by a st
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
I have no objection to removing it now, but previously I think you
agreed with Bruce's comment that we should leave it intact (but
deprecated) for 7.4, and remove in 7.5.
Did we discuss this already? I'd forgotten.
In any case, the module
> See:
> http://developer.postgresql.org/docs/postgres/functions-comparisons.html#AEN12154
>
> regression=# SELECT g.grosysid, g.groname, s.usesysid, s.usename FROM pg_shadow
> s, pg_group g WHERE s.usesysid = any (g.grolist);
These forms below are all equivalent, right?
If so ideally they w
Joe Conway kirjutas N, 28.08.2003 kell 21:15:
> Greg Stark wrote:
> > Specifically I want to know how to replace my int_array_aggregate(int) and
> > int_array_enum(_int) calls.
>
> I have no idea what those are -- are they from contrib?
>
> You can create an aggregate to turn arbitrary datatype e
Hannu Krosing wrote:
Any idea of performance - is this array_aggregate(anyelement) faster,
slower or about same than int_array_aggregate(int) ?
I haven't tested, but I'd guess for an array of any significant length
int_array_aggregate() is faster (see my other post). That's one of the
reasons I h
Joe Conway <[EMAIL PROTECTED]> writes:
> I have no objection to removing it now, but previously I think you
> agreed with Bruce's comment that we should leave it intact (but
> deprecated) for 7.4, and remove in 7.5.
Did we discuss this already? I'd forgotten.
In any case, the module isn't visi
Tom Lane wrote:
What I'm thinking of doing is removing the code, and replacing the
README with a note explaining how to convert contrib/array queries to
use the new mainstream syntaxes. That will give contrib/array users
a clue what they're supposed to do. In a release or three the README
could g
Joe Conway <[EMAIL PROTECTED]> writes:
> Greg Stark wrote:
>> And how to replace my "arr *= n" calls too.
> See:
> http://developer.postgresql.org/docs/postgres/functions-comparisons.html#AEN12154
That reminds me --- contrib/array is definitely obsolete now, and there
may be parts of the other c
Joe Conway <[EMAIL PROTECTED]> writes:
> Greg Stark wrote:
> > So where are the new array functions and syntaces documented?
>
> Mainly here:
> http://developer.postgresql.org/docs/postgres/arrays.html
excellent. thank you.
> > Specifically I want to know how to replace my int_array_aggregate(i
Greg Stark wrote:
So where are the new array functions and syntaces documented?
Mainly here:
http://developer.postgresql.org/docs/postgres/sql-expressions.html#SQL-SYNTAX-ARRAY-CONSTRUCTORS
http://developer.postgresql.org/docs/postgres/arrays.html
http://developer.postgresql.org/docs/postgres/funct
So where are the new array functions and syntaces documented?
Specifically I want to know how to replace my int_array_aggregate(int) and
int_array_enum(_int) calls. And how to replace my "arr *= n" calls too.
I think these are supposed be "ALL my_array" and "n = ANY myarray" or
something like t
11 matches
Mail list logo