From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Hans Spaans <pgsql-admin(at)lists(dot)hansspaans(dot)nl>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] concat_ws |
Date: | 2003-08-03 23:27:13 |
Message-ID: | 2804.1059953233@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)com> writes:
> But I wonder why it isn't at all a problem when the function is also
> defined STRICT?
Because the inliner doesn't think it can safely inline in that case; the
substituted expression isn't strict and so inlining would potentially
change the semantics.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-03 23:53:57 | Re: concat_ws |
Previous Message | Mendola Gaetano | 2003-08-03 23:20:21 | Re: concat_ws |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-08-03 23:30:26 | Release changes |
Previous Message | Mendola Gaetano | 2003-08-03 23:20:21 | Re: concat_ws |