pgsql: Fix test case to do what it intends to

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix test case to do what it intends to
Date: 2024-05-13 08:35:11
Message-ID: E1s6R9K-000jVs-Kz@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix test case to do what it intends to

This test case intended to fail because setting a column as generated to
the partitioned table while leaving the partition alone is not allowed;
but instead failed because of a discrepancy of not-null constraint. Fix
this by adding the not-null constraint first, then set the column as
generated in a separate ALTER TABLE command, which gets the expected
error. Also, because the next test also wants to set the column as
not-null, add a BEGIN/ROLLBACK block so that the added not-null is
removed.

Oversight in 699586315704.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/e89f4c66182e409b6643b1e8426371011dc25217

Modified Files
--------------
src/test/regress/expected/identity.out | 6 ++++--
src/test/regress/sql/identity.sql | 4 +++-
2 files changed, 7 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2024-05-13 10:23:30 pgsql: Revert structural changes to not-null constraints
Previous Message Michael Paquier 2024-05-13 03:22:02 Re: pgsql: Fix overread in JSON parsing errors for incomplete byte sequence