diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2023-04-10 13:09:18 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2023-04-10 13:09:18 -0400 |
| commit | fbbd7edca867ea8f8bd7540492e527fdb16d954b (patch) | |
| tree | 1c7cfa93af1742f8bf915d6070d2b35c8bf4fb9f /src/backend/parser/parse_utilcmd.c | |
| parent | 26f36fe844880ff68dc28493bba9aced5aad0034 (diff) | |
| download | postgresql-fbbd7edca867ea8f8bd7540492e527fdb16d954b.tar.gz postgresql-fbbd7edca867ea8f8bd7540492e527fdb16d954b.zip | |
Doc: adjust examples of EXTRACT() output to match current reality.
EXTRACT(EPOCH), EXTRACT(SECOND), and some related cases print more
trailing zeroes than they used to. This behavior change happened
with commit a2da77cdb (Change return type of EXTRACT to numeric),
and it was intentional according to the commit log:
- Return values when extracting fields with possibly fractional
values, such as second and epoch, now have the full scale that the
value has internally (so, for example, '1.000000' instead of just
'1').
It's been like that for two releases now, so while I suggested
changing this back, it's probably better to adjust the documentation
examples.
Per bug #17866 from Евгений Жужнев. Back-patch to v14 where the
change came in.
Discussion: https://postgr.es/m/17866-18eb70095b1594e2@postgresql.org
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions