DeJuan Jackson <djackson@speedfc.com> writes:
> I have a suspicion that the version might be different. I have the same
> symptom here on two different RH 7.3 boxes one running 7.3.2 and the
> other running 7.3.3
> It would appear 7.3.2 is more strict about the naming of the GROUP BY
> fields.
Hmm ... digging in the CVS logs, I see just two potentially-relevant
changes between 7.3.2 and 7.3.3.
2003-04-03 13:04 tgl
* src/backend/parser/parse_agg.c (REL7_3_STABLE): Repair incorrect
checking of grouped/ungrouped variables in the presence of unnamed
joins; per pghackers discussion 31-Mar-03.
(the discussion in question is at
http://archives.postgresql.org/pgsql-hackers/2003-03/msg01230.php
2003-03-13 11:58 tgl
* src/backend/optimizer/plan/planner.c (REL7_3_STABLE): GROUP BY
got confused if there were multiple equal() GROUP BY items. This
bug has been latent since 7.0 or maybe even further back, but it
was only exposed when parse_clause.c stopped suppressing duplicate
items (see its rev 1.96 of 18-Aug-02).
The second one doesn't seem to apply, but maybe the first does.
regards, tom lane