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.94.2) (envelope-from ) id 1qWdBt-003rXv-1C for pgsql-general@arkaria.postgresql.org; Thu, 17 Aug 2023 13:37:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qWdBq-0004g2-T4 for pgsql-general@arkaria.postgresql.org; Thu, 17 Aug 2023 13:37:31 +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.94.2) (envelope-from ) id 1qWdBq-0004fu-Fd for pgsql-general@lists.postgresql.org; Thu, 17 Aug 2023 13:37:30 +0000 Received: from mout-u-107.mailbox.org ([2001:67c:2050:101:465::107]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qWdBn-000fnX-Ku for pgsql-general@lists.postgresql.org; Thu, 17 Aug 2023 13:37:29 +0000 Received: from smtp102.mailbox.org (smtp102.mailbox.org [IPv6:2001:67c:2050:b231:465::102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-107.mailbox.org (Postfix) with ESMTPS id 4RRQzP5fHfz9sRt; Thu, 17 Aug 2023 15:37:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1692279441; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Zu6fOzx5OC8ciq9YzoDhu42fDZs29ZD1gYUayKXC3mI=; b=tRUARvXIsHDoFHA88fUNX2QA/VVkJeSMQSjSJpVvoLwpu0JOXUnI55QPkMOcKKspw6gvtg W962SHJann1FImEegxH2z+76Fik12TQeKOYViDhE0kc8qpGSG9YZzX7pgZnkTDY0aa0lof 9DSjGysvHN7DpOia34yvxlSj/ylJwbTBD8nCvUZPygOSBY9GIm3AFKw6wTSDlBFNIi0m/r HvRTMyrhEHpjsLeUWLLSMJIEgLP4xuYYbk9wNShH84gzhf8ObR/FopV81hRtBMAg+aXYr/ Qm/2jcMlDIu8omwpcz46qaffr2cACkG6o6hGyrv5uUNDfvSZOf0vDJmZZ0RvyA== Date: Thu, 17 Aug 2023 15:37:21 +0200 (CEST) From: Erik Wienhold To: Tom Lane Cc: "pgsql-general@lists.postgresql.org" Message-ID: <2102137877.358573.1692279441321@office.mailbox.org> In-Reply-To: <1819966.1692278294@sss.pgh.pa.us> References: <533487381.212078.1692100096551@office.mailbox.org> <84bd46dba5ec4097ba9663f46a1e5754@quipsy.de> <400164688.228966.1692109673749@office.mailbox.org> <015a3586e6dc40e0b1c3a4a1f3b1e44c@quipsy.de> <1819966.1692278294@sss.pgh.pa.us> Subject: Re: AW: AW: Cast INTEGER to BIT confusion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Rspamd-Queue-Id: 4RRQzP5fHfz9sRt List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 17/08/2023 15:18 CEST Tom Lane wrote: > > That's probably because the grammar uses SystemTypeName (effectively > prepending "pg_catalog.") for any type that has special syntax called > out in the SQL standard. You could get around that in various ways, > but they all involve changing the way the CREATE TABLE command is > written, because just plain "BIT" is a SQL-mandated special case. The answer I was looking for. Thanks Tom. -- Erik