Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vdbZc-002gc9-0J for pgsql-general@arkaria.postgresql.org; Wed, 07 Jan 2026 22:00:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vdbZb-00Fiad-08 for pgsql-general@arkaria.postgresql.org; Wed, 07 Jan 2026 22:00:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vdbZa-00FiaV-2E for pgsql-general@lists.postgresql.org; Wed, 07 Jan 2026 22:00:11 +0000 Received: from mail-oo1-xc30.google.com ([2607:f8b0:4864:20::c30]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vdbZY-0059YY-1u for pgsql-general@postgresql.org; Wed, 07 Jan 2026 22:00:11 +0000 Received: by mail-oo1-xc30.google.com with SMTP id 006d021491bc7-65b6b69baf8so870866eaf.3 for ; Wed, 07 Jan 2026 14:00:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ridewithvia.com; s=google; t=1767823207; x=1768428007; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TlGUB7A1BdZcHPyY6iz7gh+zIagwh8lCN5x0or6bFGk=; b=NBgBb/7fmC5ajAlDEuYp0BYW7ZAk+H7VMyiTr6mA3kHP5Lx0Lc7BGNwU7A0vTlXDoZ gdUSee1jEQSTWe6ViPhamD6Q9JFWih9PFgTZQhO+zJsCIY2eQFy8/0BvnJ/uJivP1Xvj lcrCycu7ICvzzyzDjmexbX1Pb/9JWDjH57FjM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1767823207; x=1768428007; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=TlGUB7A1BdZcHPyY6iz7gh+zIagwh8lCN5x0or6bFGk=; b=Rges+hnZ1W/uZFrogiMV5c0dSqhvwM4XiVeP8gLoG1GdJYAD+EvmtXGOUCXm7DRpcr CAfgCGd/Oy8DqlKkkg60PluG8zb7neGPvV/nqm8ETYbh7x+gPfd1/2aTmud6DOq0Nujn BZGmSyPPMxj5mzhxffb+ScQjWFXqM8YXKf58cOSAMHv974K0dXoOx1IQBpdd3kelA6Ev JRs3LzBzEqEGEcrlCy4XT4B9XSv4zG9AYhaCkOodZSwwHvou/AH+GXVt2mb6YP3MmQlC rgIy0s1oHtjSJs2vG6hWM5Yel4PqRuo2N/Ov6EeD7Hx/EZUIx+Z1U+4uYXD3jwBCQUbg IDfw== X-Gm-Message-State: AOJu0Yx4w4ALHrmrvXT4HvkKBa5aEAdYcUi6cTxMENX/Ju3o4QrvNGCQ BJfJi4J3zr2PypJH+GH1g/vzI9ilpKQHQ2khuHwAqn4/ozJeynUIIcKqKV3SzXkNWQTd4rLIuSN yG+i4qjVwTbxUHW4AIUd2Baw8LIYiV37nwJW4NsghHhZ3LGAAAdiJhg/lHGUIvSO1pMWYeszrg+ uSbiEohdUsdBbq2YqaOHp0xGhKXtvK3y4tyeNIEx7V2VZzvWg= X-Gm-Gg: AY/fxX5jRDxKrRvN/qZQOopn8W+62k2GWNyJE2/cmCixTqvovIndTuHHPdx7mSFNSUg bYlbOZWBpUcLgaz3l7fZFjZItGh1N38bxjFuiC83caRnpBJjBXwokqDNwmdPP4xt7CEq2+Qn/al RDxDPwdiAhY4K6eC+lmepinVnlrAagffqoPujbXZAI2OHkY520e4enDN9UgkT7oyzyDoh0h3uop ZaqGFYT8y+Jn3fkZuTLItEJJRxMwqODOVWfTMN3uk3IGO3wqO0cpseaP8jvxu3w18tk9g== X-Google-Smtp-Source: AGHT+IEi+b/vpHWo2TN+7N1SpGhMpvIRlfQ9hqk34eHGMKge5p+pQ2Xi8J8YnNtSGsxVCLkenMBJSMiI1LvtZ7f6tc0= X-Received: by 2002:a05:6820:2d8f:20b0:65f:5c88:67b4 with SMTP id 006d021491bc7-65f5c8869admr347574eaf.81.1767823205886; Wed, 07 Jan 2026 14:00:05 -0800 (PST) MIME-Version: 1.0 References: <13cb8c5c-84f1-4bf8-983a-268969bfcc25@aklaver.com> In-Reply-To: <13cb8c5c-84f1-4bf8-983a-268969bfcc25@aklaver.com> From: Stuart Campbell Date: Thu, 8 Jan 2026 08:59:52 +1100 X-Gm-Features: AQt7F2o4nClTisT6efXRZDJKdnJeoW-7y3qkIBx5kLl9EfSCXJDEo42tE3qaaNk Message-ID: Subject: Re: Unexpected modification of check constraint definition To: Adrian Klaver Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="00000000000036e22a0647d36acf" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000036e22a0647d36acf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 8, 2026 at 2:24=E2=80=AFAM Adrian Klaver 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 --=20 This communication and any attachments may contain confidential information= =20 and are intended to be viewed only by the intended recipients. If you have= =20 received this message in error, please notify the sender immediately by=20 replying to the original message and then delete all copies of the email=20 from your systems. --00000000000036e22a0647d36acf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jan 8, 2026 at 2:24=E2=80=AFAM Adrian= Klaver <adrian.klaver@akla= ver.com> wrote:
https://www.postgresql.org/docs/curre= nt/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. I= t seems like I should generally prefer to use text over varchar. (I've = read advice along those lines elsewhere.)
=C2=A0
When you did the dump/restore cycles where they from and to the same
Postgres version/instance?

Yes. In the exam= ple I provided, that was all from the same Postgres 16.4 instance.=C2=A0

Regards,
Stuart

This communication and any attachments may contain confidential inform= ation 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.


--00000000000036e22a0647d36acf--