Re: Unexpected modification of check constraint definition

From: Stuart Campbell <stuart(dot)campbell(at)ridewithvia(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Unexpected modification of check constraint definition
Date: 2026-01-07 21:59:52
Message-ID: CAAZ6SnweFKohrh9UecMLUtR7CJ5d=qNfjbfPyAJD_-b5O1XM8A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jan 8, 2026 at 2:24 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:

> https://www.postgresql.org/docs/current/datatype-character.html
>
> "text is PostgreSQL's native string data type, in that most built-in
> functions operating on strings are declared to take or return text not
> character varying. For many purposes, character varying acts as though
> it were a domain over text."

Thanks. It seems like I should generally prefer to use text over varchar.
(I've read advice along those lines elsewhere.)

> When you did the dump/restore cycles where they from and to the same
> Postgres version/instance?

Yes. In the example I provided, that was all from the same Postgres 16.4
instance.

Regards,
Stuart

--
This communication and any attachments may contain confidential information
and are intended to be viewed only by the intended recipients. If you have
received this message in error, please notify the sender immediately by
replying to the original message and then delete all copies of the email
from your systems.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2026-01-07 22:24:01 Re: Unexpected modification of check constraint definition
Previous Message Stuart Campbell 2026-01-07 21:55:50 Re: Unexpected modification of check constraint definition