| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, James Coleman <jtc331(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Should we document how column DEFAULT expressions work? |
| Date: | 2024-10-17 04:28:25 |
| Message-ID: | 571695.1729139305@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrei Lepikhov <lepihov(at)gmail(dot)com> writes:
> Pardon the noise, but can you consider the idea of replacing the phrase
> 'data insertion time' with something like 'immediately before the
> insertion operation starts'? Sometimes people (especially younglings)
> ask which time it is precisely: will it differ for each tuple?
If we're discussing the meaning of "now", it's the transaction
start timestamp, cf
https://www.postgresql.org/docs/devel/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT
I do not think other wordings will improve on that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seino Yuki | 2024-10-17 05:07:32 | Re: Doc: shared_memory_size_in_huge_pages with the "SHOW" command. |
| Previous Message | Michael Paquier | 2024-10-17 04:24:50 | Re: BF mamba failure |