Re: Should we document how column DEFAULT expressions work?

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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-06-27 11:57:37
Message-ID: ef4d9b38-b7a5-4c85-ba12-062929c2d136@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 27.06.24 02:34, David Rowley wrote:
> For the special timestamp stuff, that place is probably the special
> timestamp table in [1]. It looks like the large caution you added in
> 540849814 might not be enough or perhaps wasn't done soon enough to
> catch the people who read that part of the manual before the caution
> was added. Hard to fix if it's the latter without a time machine. :-(

Maybe we should really be thinking about deprecating these special
values and steering users more urgently toward more robust alternatives.

Imagine if 'random' were a valid input value for numeric types.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2024-06-27 12:00:33 Re: Doc: fix track_io_timing description to mention pg_stat_io
Previous Message Ranier Vilela 2024-06-27 11:50:03 Re: Avoid incomplete copy string (src/backend/access/transam/xlog.c)