From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Jan Wieck <jwieck(at)debis(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
Subject: | Re: [HACKERS] CREATE FUNCTION broken |
Date: | 1998-02-13 16:16:52 |
Message-ID: | 34E471F4.A3AF69BF@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > Someone changed the parser to build a TypeName node on CREATE
> > > FUNCTION in any case. As a side effect, ALL! functions
> > > created got the proretset attribute to true. Thus for a
> > > SELECT the parser wrapped an Iter node around the Expr and
> > > since singleton functions set isDone the Iter returns no
> > > tuple up.
> > It looks like your patch will completely fix things, and is better than my
> > reverting the gram.y code. Can you suggest a small test case to include in
> > the regression suite?
> The regression tests found it - but you wouldn't expect it
> there. It's in the trigger test, where at some places SELECT
> set_ttdummy(0) returns 0 columns instead of one.
Ah! This might be all of the problem with the trigger regression test then? I
had wanted Vadim to look at it because I wasn't sure what the behavior should
be. Does this test look good to you now?
> Even if reverting the gram.y code - my patch could only make
> things better.
Yes, and scrappy already applied it :)
- Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-02-13 16:22:32 | Re: [HACKERS] Unsubscribe |
Previous Message | Magnus Nslund | 1998-02-13 16:16:31 | pgsql and threads don't match |