Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1phcD9-0003KI-EU for pgsql-general@arkaria.postgresql.org; Wed, 29 Mar 2023 20:15:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1phcD7-0001wd-KR for pgsql-general@arkaria.postgresql.org; Wed, 29 Mar 2023 20:15:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1phcD7-0001wT-7S for pgsql-general@lists.postgresql.org; Wed, 29 Mar 2023 20:15:57 +0000 Received: from mail-ed1-x52a.google.com ([2a00:1450:4864:20::52a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1phcD3-0008Kb-J2 for pgsql-general@lists.postgresql.org; Wed, 29 Mar 2023 20:15:55 +0000 Received: by mail-ed1-x52a.google.com with SMTP id r11so68141161edd.5 for ; Wed, 29 Mar 2023 13:15:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680120951; x=1682712951; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=lYzvuiqkbMU2CkLKJOGyY3ZoJKN01eNCl8x+nAtDH7M=; b=Gfk5PmKLzHLZ9GxA5AXKfSynR0+or6VZC6MHLeEpHvkwbDVGaS0aPph4icghWYYSko qGPh/gkyEIFPNWqnLmqAnMXKiMjwGHLmEsazS/hgYqaepJyPD3Dj0xNXN/bLsFyYpYn+ CdLEProWhd+WjcYHxNNDW/28bkgqnDsW7Bt6pDYpAkOqT9dObSMX4FJqJHJtv1Fu8ec0 e06NLeYv8ymOrT76fBeKud/LO6WmZXm2bXJ8OW1dPW3OjKQB22a9dSf4jbZ1J5lNhmNF a/Y4YvgUHjlWU/0NRZCFdPir6FL48MuJRd29bfhfDZn5azDNuqM25OPZWXu659OWYaHy 0jNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680120951; x=1682712951; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=lYzvuiqkbMU2CkLKJOGyY3ZoJKN01eNCl8x+nAtDH7M=; b=tQHxw+RkqX/TnMNZQeSzjTSiaHEGJEQr/0djHUNwDA8VrvGBv6MXk02iUg2+fRGrOW srMlN275CxiD+2JWnAGrKF9Bs1ia7PifKNix9NSIzPPxPZawUBCPt+vK9LagdVmYm8E1 90IwO2aE7YISO5MHWZ3ZeZSDrMgmqoGmMA/4lQxsrkT00HhUXJsOrwEPwmT8hNMAyV+8 /74Nh2w8AayJMyE46B5HnFjBMpihLkiQH6TVB74Poa2L0VqnYS45cJfUrWnYGNlxvQUi 3Y7UH+SOKbU9NXbu5c1oco5pCOydptqXews7jI59uuI8nVRJCwO3+HZLeKuefKNg/XlY /vvg== X-Gm-Message-State: AAQBX9eZZAfDcLb+wfuUcIymtuXdwynkuM2dNl6YeDvFALN5da0QTrAA mxr4A+yTLl860gCt+c4NJIg= X-Google-Smtp-Source: AKy350Y2tfovbBX8u8EFOKGDl1liLAWV/Y5uGq5xvJixP0G3Dg1Eb3afbcqJ63Vew6jPlQqOJkYKhw== X-Received: by 2002:a05:6402:1149:b0:4fc:5888:473a with SMTP id g9-20020a056402114900b004fc5888473amr22111397edw.9.1680120950952; Wed, 29 Mar 2023 13:15:50 -0700 (PDT) Received: from hollewijn.internal (217-19-30-105.dsl.cambrium.nl. [217.19.30.105]) by smtp.gmail.com with ESMTPSA id q27-20020a50aa9b000000b004af73333d6esm17372863edc.53.2023.03.29.13.15.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2023 13:15:50 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Re: Using CTID system column as a "temporary" primary key From: Alban Hertroys In-Reply-To: Date: Wed, 29 Mar 2023 22:15:48 +0200 Cc: Adrian Klaver , Kirk Wolak , Geoff Winkless , pgsql-general Content-Transfer-Encoding: quoted-printable Message-Id: <875C63FC-D302-4D2C-B546-FD0D957419F2@gmail.com> References: To: Sebastien Flaesch X-Mailer: Apple Mail (2.3608.120.23.2.7) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 29 Mar 2023, at 21:11, Sebastien Flaesch = wrote: >=20 > Oh the use of default keyword is new to me, thanks for that. >=20 > But to make PostgreSQL more Informix-compatible, zero should have been = considered as well. =E2=80=A6No, I=E2=80=99m not going to be humble about this opinion=E2=80=A6= Postgres does a sane thing here. It=E2=80=99s Informix that you should be complaining about. Zero is not = a sane value to specify special behaviour, it could mean zero and be = just as valid. By consequence, Informix probably forbids zero as a = sequence value, but that is an artefact (and a limitation) of its = implementation, not a feature. The core of your problem however, is that you=E2=80=99re trying to get = database-agnostic behaviour by relying on database-specific features. = That is not going to work, you=E2=80=99ve just been lucky enough to get = away with it until now. There=E2=80=99s really only one realistic answer here: Fix your design. Regards, Alban Hertroys -- There is always an exception to always.