| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: plpgsql - Assert statement |
| Date: | 2015-01-27 23:13:29 |
| Message-ID: | 54C81B99.50405@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/27/15 1:30 PM, Pavel Stehule wrote:
> I don't see the separate warning as being helpful. I'd just do something like
>
> + (err_hint != NULL) ? errhint("%s", err_hint) : errhint("Message attached to failed assertion is null") ));
>
>
> done
>
>
> There should also be a test case for a NULL message.
>
>
> is there, if I understand well
I see it now. Looks good.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-01-27 23:16:02 | Re: proposal: row_to_array function |
| Previous Message | Jim Nasby | 2015-01-27 23:09:00 | Re: pg_upgrade and rsync |