| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-committers(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Avoid premature free of pass-by-reference CALL arguments. |
| Date: | 2018-03-25 02:55:26 |
| Message-ID: | 11488.1521946526@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-02-10 18:37:17 +0000, Tom Lane wrote:
> CALL ptest1(substring(random()::text, 1, 1)); -- ok, volatile arg
> At first I was gosh darned confused, this really didn't seem likely to
> be an LLVM induced failure. And it turns out it isn't. If the value
> returned by random() is very small, the text representation switches to
> scientific notation like 8.26204195618629e-05.
Ooops. I'll do something about that tomorrow.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-03-25 03:05:52 | Re: pgsql: Add long options to pg_resetwal and pg_controldata |
| Previous Message | Peter Eisentraut | 2018-03-25 01:53:06 | pgsql: Add long options to pg_resetwal and pg_controldata |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-25 03:14:34 | Re: Using base backup exclusion filters to reduce data transferred with pg_rewind |
| Previous Message | Thomas Munro | 2018-03-25 02:38:14 | Re: JIT compiling with LLVM v12.2 |