| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Strange behavior of function date_trunc |
| Date: | 2021-05-06 14:28:56 |
| Message-ID: | CAKFQuwah23MXaq=hO8HvHJc3b9Thb9LR_HP3DgUpYuUKxtXemQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, May 6, 2021 at 6:44 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This case is the reason we invented the "stable" attribute to begin
> with. People have since misinterpreted it as authorizing caching of
> function results, but that's not what it was intended for.
>
>
This is a good paragraph...if something like it gets added to the create
function documentation mis-interpretations are likely to decrease. I
personally did not draw this conclusion after having read that particular
piece of documentation multiple times over the years.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Boussekey | 2021-05-06 14:29:39 | [RPM/CentOS7] Need to disable repo_gpgcheck on pgdg-common when using RPM version 42.0-17.1 |
| Previous Message | Tom Lane | 2021-05-06 13:44:48 | Re: Strange behavior of function date_trunc |