Re: date/time special values incorrectly cached as constant in plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tijs van Dam <tijs(at)thalex(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: date/time special values incorrectly cached as constant in plpgsql
Date: 2020-10-17 20:05:54
Message-ID: 137473.1602965154@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> Indeed, but I concur with the OP that 8.5.1.4 doesn't really expend enough
> words on this point.

After a bit more thought, I committed

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=540849814cdc22ea025777d374ff6705b4d64a0f

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2020-10-17 22:58:23 Re: BUG #16604: pg_dump with --jobs breaks SSL connections
Previous Message Tom Lane 2020-10-17 16:18:16 Re: date/time special values incorrectly cached as constant in plpgsql