Re: server crash: displaying sqlerrm in exception block

From: "Asif Ali" <asifalirehman(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: server crash: displaying sqlerrm in exception block
Date: 2007-02-08 20:00:32
Message-ID: c5110cc50702081200r55962f66sca39a49453b99e4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,
well i just updated the code and found your patch is applied in there and
it's working. may be i missed something while applying your patch.

Regards,
--Asif

On 2/8/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Asif Ali" <asifalirehman(at)gmail(dot)com> writes:
> > here is the test case
>
> It works for me:
>
> regression=# select func();
> INFO: sql error msg ex -----
> INFO: sql error msg ex -----
> INFO: sql error v_msg ex -----
> func
> ------
> 0
> (1 row)
>
> Are you sure you applied the patch correctly? In particular, you'd need
> a working version of bison to rebuild the gram.y file --- the behavior
> you're reporting sounds like what would happen if that hadn't gotten
> rebuilt.
>
> regards, tom lane
>

--
Regards,
--Asif Ali Rehman

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2007-02-09 04:21:39 Re: [BUGS] wrong behavior using to_char()
Previous Message Bruce Momjian 2007-02-08 16:57:19 Re: BUG #2975: UNIQUE INDEX doesn't work