Re: [HACKERS] 6.4 Aggregate Bug

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: daybee(at)bellatlantic(dot)net, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] 6.4 Aggregate Bug
Date: 1998-08-02 04:21:05
Message-ID: 35C3E931.F2E58F34@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > > While testing my 6.4 patch I
> > > came across a nasty little bug.
> > Nor in my cvs tree from around the second week in July...
> > Haven't tried a current source tree...
> Can someone CVS back in time to find the date it broke?

I haven't done that yet. I _did_ do a CVSup just now and in the parser
area I do have an uncommitted patch for parse_clause.c in the
transformSortClause() routine. It was to help with type matching on
whatever Bruce and I were fixing a couple of weeks ago, before the docs
and Applix/iodbc became a higher priority. Anyway, don't know if that is
helping David's symptoms or not, or whether the breakage is in another
part of the code. Nothing else is any different in the parser area of
the code (except for gram.c, which shouldn't be an issue?).

I'll go ahead and commit the code tonight or tomorrow and then David or
you can see if it helps. Will post some e-mail when it happens...

- Tom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter T Mount 1998-08-02 09:26:11 Re: [HACKERS] Problem with CVS access to current sources
Previous Message Brett McCormick 1998-08-02 02:29:24 follow up Re: [HACKERS] SPI_connect always fails.