Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Current sources?

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: David Gould <dg(at)illustra(dot)com>
Cc: Tom Ivar Helbekkmo <tih+mail(at)Hamartun(dot)Priv(dot)NO>, pgsql-hackers(at)postgreSQL(dot)org, t-ishii(at)sra(dot)co(dot)jp, daveh(at)insightdist(dot)com
Subject: Re: [HACKERS] Current sources?
Date: 1998-05-25 22:43:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, 25 May 1998, David Gould wrote:

> Ok, I think I have found the source of the dropconns on "delete" querys
> that are causing the current problem. The change listed below sets
> tupType to the junkFilter (whatever that is) jf_cleanTupType unconditionally.
> This makes a SEGV later as the tupType ends up NULL.
> Here is what CVS says:
>     ---------------
>     revision 1.46
>     date: 1998/05/21 03:53:50;  author: scrappy;  state: Exp;  lines: +6 -4
>     From: David Hartwig <daveh(at)insightdist(dot)com>
>     Here is a patch to remove the requirement that ORDER/GROUP BY clause
>     identifiers be included in the target list.
>     --------------
> I do not believe that this could ever have passed regression. Do we have
> the whole patch to back out, or do we need to just "fix what we have now"?

	fix what we have now...if its possible...

> Also, perhaps we need to be more selective about checkins? 

	We're in an alpha/development phase general opinion on
that is that I'd rather someone throw in code that is 95% good, with 5%
error, then nobody making a start anywhere...

	Until a Beta freeze, *never* expect the server to actually
work...if it does, bonus.  

Marc G. Fournier                                
Systems Administrator @ 
primary: scrappy(at)hub(dot)org           secondary: scrappy(at){freebsd|postgresql}.org 

In response to

pgsql-hackers by date

Next:From: t-ishiiDate: 1998-05-26 02:09:08
Subject: Re: [HACKERS] Current sources?
Previous:From: Bruce MomjianDate: 1998-05-25 22:30:16
Subject: Re: [HACKERS] Current sources?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group