Oh, sure I understand. There were a number of people mentioning the
core issue. What the core/major folks do is more give information about
historical or practical ideas behind certain issues, so in that way they
do have a strong voice, but only in the way their ideas effect other
people's opin
Bruce,
> I have seen a few mentions in the past weeks about core vs. non-core
> developers. I should reiterate that the core group feels there is no
> distinction between the opinions of the core people and the other
> major
> developers. Everyone gets just one vote.
Which is why it's importan
Josh Berkus wrote:
>
> Adam,
>
> > I do a lot of reporting based on such SQL statements. Counting rows from
> > large datasets. Since the PG gurus don't seem to think this is such a big
> > deal can someone enlighten me as to why?
>
> I am not a core developer, but I will take a crack at your
Josh Berkus <[EMAIL PROTECTED]> writes:
> For Postgres custom aggregates, using a standard index is impossible, for
> reasons I think are obvious.
> That leaves MAX, MIN, and COUNT.All of these aggregates should, in an
> ideal world, be index-responsive for large data sets.
While it's fair
Adam,
> I do a lot of reporting based on such SQL statements. Counting rows from
> large datasets. Since the PG gurus don't seem to think this is such a big
> deal can someone enlighten me as to why?
I am not a core developer, but I will take a crack at your question anyway
based on my perso
