Re: Should we document how column DEFAULT expressions work?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(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 00:55:04
Message-ID: ZxBgaMZCOwKsGSuu@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 16, 2024 at 04:45:39PM -0700, David G. Johnston wrote:
> On Wednesday, October 16, 2024, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I do not, but maybe I’m being overly pedantic.  All string literals are parsed
> during the create table command.  It’s only the situations where that parsing
> is non-deterministic that cause an issue.
>
> Is there anything wrong with the patch I proposed?

I thought it was too verbose so the point was not clear.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2024-10-17 01:02:48 Re: ltree docs imprecise about sorting order
Previous Message Andy Fan 2024-10-17 00:33:44 Re: MergeAppend could consider sorting cheapest child path