From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
---|---|
To: | Dave Trombley <dtrom(at)bumba(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: plpgsql and rowtypes |
Date: | 2002-01-02 15:25:50 |
Message-ID: | 200201021525.g02FPof06751@saturn.jw.home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dave Trombley wrote:
> Dave Trombley wrote:
>
> > I'm using the current release version (7.1.3), downloaded and
> > compiled it today after having this problem. I'm going to try it
> > again on a fresh box, in case something funcky is going on with
> > library versions, etc.
> >
> Ok, yeah, now I'm pretty sure I'm not insane. Well, maybe not /so/
> sure. =) But, I've messed up pl_exec.c to dump some information about
> the branches it's taking in an IF statement. It seems that the false
> body part in the PLpgSQL_stmt_if structure is not being set correctly in
> a IF-THEN-ELSIF-ELSE (same example as before):
Sometimes I wonder why nobody uses
#option dump
That in the first line of the procedure body causes the
backend to produce alot of useful information in the
postmaster log.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-01-02 16:12:19 | Re: plpgsql and rowtypes |
Previous Message | P.J. "Josh" Rovero | 2002-01-02 13:43:59 | Re: Possible bug with shared memory buffers |