#35368: Postgres schema test failure locally
-------------------------------------+-------------------------------------
     Reporter:  bcail                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):

 Nailed it down to [https://www.postgresql.org/docs/release/15.6/ a change
 in Postgres 15.6 released on 2024-02-08] so it makes sense that bcail ran
 on that only recently against PG 15.

 > **Fix function volatility checking for GENERATED and DEFAULT expressions
 (Tom Lane)**
 >
 > These places could fail to detect insertion of a volatile function
 default-argument expression, or decide that a polymorphic function is
 volatile although it is actually immutable on the datatype of interest.
 **This could lead to improperly rejecting or accepting a GENERATED clause,
 or to mistakenly applying the constant-default-value optimization in ALTER
 TABLE ADD COLUMN**.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35368#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ecf40571e-adda184b-74d7-42af-a0a2-b67530c3cbb6-000000%40eu-central-1.amazonses.com.

Reply via email to