Re: Unexpected modification of check constraint definition
| От | Stuart Campbell |
|---|---|
| Тема | Re: Unexpected modification of check constraint definition |
| Дата | |
| Msg-id | CAAZ6SnweFKohrh9UecMLUtR7CJ5d=qNfjbfPyAJD_-b5O1XM8A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Unexpected modification of check constraint definition (Adrian Klaver <adrian.klaver@aklaver.com>) |
| Список | pgsql-general |
On Thu, Jan 8, 2026 at 2:24 AM Adrian Klaver <adrian.klaver@aklaver.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.
В списке pgsql-general по дате отправления: