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 1kmCPy-0001jB-Du for pgsql-docs@arkaria.postgresql.org; Mon, 07 Dec 2020 09:02:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kmCPx-0003FZ-7A for pgsql-docs@arkaria.postgresql.org; Mon, 07 Dec 2020 09:02:49 +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 1kmCPx-0003FS-1b for pgsql-docs@lists.postgresql.org; Mon, 07 Dec 2020 09:02:49 +0000 Received: from mail-ed1-x52d.google.com ([2a00:1450:4864:20::52d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kmCPv-00045Y-3k for pgsql-docs@lists.postgresql.org; Mon, 07 Dec 2020 09:02:48 +0000 Received: by mail-ed1-x52d.google.com with SMTP id k4so12903244edl.0 for ; Mon, 07 Dec 2020 01:02:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version; bh=p40rknU4MoTE/KeKScLmKFBSVihuRnt3C0Rc5UNRmJg=; b=h+l71U7fNWiFC2jJjtwebXnWPnZnIcENgiMPZXIuxLOSqPum/80/7iNVqHElGpspuV 9gV3KhXsjcNH9CLVGH6nOwUdUlz+dICkqNwkX2+Ck3NWn8LhYRhF24ggwkr9GOpUpSah gzMK8rz8j2VyFcoHIpQmqiHE+Wr7PrAD650rJAiM+2zKiOR3qbG+IN396okQrpBBdv/y J0zhABXC1kSUL6fyj1WWdXMch8xnm3JSltjGLBol9sTFaeka7bHeNalYMLCc2x1tRlqN IKL0D2aQj38sjPuZKTuJueGjfV1XLo83D1LBek+CIVcU/c0n/HTZl+SSqmhOP4mtpeWl 3LMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version; bh=p40rknU4MoTE/KeKScLmKFBSVihuRnt3C0Rc5UNRmJg=; b=cb2TSZ4U5VcwCv3SFNBKTJWZdXnEK0LbMZ04ODH6uhRBw3vRYPU1xaqWUJTd+Xa2I3 NaGX8j+eO6HG6yWRcVl3nu+eEmuiNGizI1NSSOQupjRSqE+ROeaS3+xxyxPgWnIoWmcn wzFIkKfGaV/HGihhyfbIBf6d+fePenXs3Ka3EKy8VnbL2/ig+r3P39y8X0Sfc0PR9QL+ rnv9/Uc4EHdw4VaLqnDFXfxrmBjeGI1F1GHngr+6gkALnYAp7+GUFoSfNLoDI10oP0G/ MTdlbQJaxRzxoLRcKi1RZshWrkvG2WCJTG61SVlvX8mffq6i2/VhxXBFy87Og2UnlKuG StVQ== X-Gm-Message-State: AOAM532bYZFrIYy0vOI5/yFpGhvCvBHI5AwLEc13pAzR9Z2vAEmJuLLv FwCnC41LyRcL+zKjYuB0RWyoFQ== X-Google-Smtp-Source: ABdhPJyWgtIgJiOff9yvC3w8ZF309zKF9VVJaHNbRg74QsGeBnE067+Iej35XoXD98kxux4mHZakzQ== X-Received: by 2002:a50:a40a:: with SMTP id u10mr18285218edb.16.1607331764751; Mon, 07 Dec 2020 01:02:44 -0800 (PST) Received: from localhost.localdomain (217-149-172-51.nat.highway.telekom.at. [217.149.172.51]) by smtp.gmail.com with ESMTPSA id m7sm10888561ejo.125.2020.12.07.01.02.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 07 Dec 2020 01:02:44 -0800 (PST) Message-ID: <0f0470f6d8c543793d2b71913cb230daea1aef3a.camel@cybertec.at> Subject: Re: Mention invalid null byte sequence From: Laurenz Albe To: bugs-postgresql@antipoul.fr, pgsql-docs@lists.postgresql.org Date: Mon, 07 Dec 2020 10:02:43 +0100 In-Reply-To: <160720552914.710.16625261471128631268@wrigleys.postgresql.org> References: <160720552914.710.16625261471128631268@wrigleys.postgresql.org> Content-Type: multipart/mixed; boundary="=-IJd/WNdGqzh2gcaPUteZ" User-Agent: Evolution 3.36.5 (3.36.5-1.fc32) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --=-IJd/WNdGqzh2gcaPUteZ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Sat, 2020-12-05 at 21:58 +0000, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/datatype-character.html > Description: > > I discovered accidentally that PostgreSQL doesn't accept null byte in text > type. It seems that Oracle does (see > https://www.postgresql.org/message-id/de752e01-f36c-821e-9181-cfba78c0fbc8%40propaas.com) > and SQLite does it too. > > So it should written in the character type that null byte are not accepted, > it would make like easier to migrate to PostgreSQL :) +1; how about the attached patch? Yours, Laurenz Albe --=-IJd/WNdGqzh2gcaPUteZ Content-Disposition: attachment; filename="Document-that-NUL-characters-are-not-supported.patch" Content-Transfer-Encoding: base64 Content-Type: text/x-patch; name="Document-that-NUL-characters-are-not-supported.patch"; charset="UTF-8" ZGlmZiAtLWdpdCBhL2RvYy9zcmMvc2dtbC9jaGFyc2V0LnNnbWwgYi9kb2Mvc3JjL3NnbWwvY2hh cnNldC5zZ21sCmluZGV4IGNlYmMwOWVmOTEuLjc1MjViNWM1NmUgMTAwNjQ0Ci0tLSBhL2RvYy9z cmMvc2dtbC9jaGFyc2V0LnNnbWwKKysrIGIvZG9jL3NyYy9zZ21sL2NoYXJzZXQuc2dtbApAQCAt MTAyMyw2ICsxMDIzLDExIEBAIENSRUFURSBDT0xMQVRJT04gaWdub3JlX2FjY2VudHMgKHByb3Zp ZGVyID0gaWN1LCBsb2NhbGUgPSAndW5kLXUta3MtbGV2ZWwxLWtjLXRyCiAgICB3aXRoIG1vc3Qg YnV0IG5vdCBhbGwgc2VydmVyLXNpZGUgZW5jb2RpbmdzLgogICA8L3BhcmE+CiAKKyAgPHBhcmE+ CisgICBBbm90aGVyIHJlc3RyaWN0aW9uIGlzIHRoYXQgUG9zdGdyZVNRTCBkb2VzIG5vdCBzdXBw b3J0IHRoZSBOVUwgY2hhcmFjdGVyCisgICAoQVNDSUkgMCkgaW4gY2hhcmFjdGVyIHN0cmluZ3Ms IHJlZ2FyZGxlc3Mgb2YgdGhlIGNoYXJhY3RlciBzZXQgdXNlZC4KKyAgPC9wYXJhPgorCiAgICA8 c2VjdDIgaWQ9Im11bHRpYnl0ZS1jaGFyc2V0LXN1cHBvcnRlZCI+CiAgICAgPHRpdGxlPlN1cHBv cnRlZCBDaGFyYWN0ZXIgU2V0czwvdGl0bGU+CiAK --=-IJd/WNdGqzh2gcaPUteZ--