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 1leC15-00067h-VI for pgsql-docs@arkaria.postgresql.org; Wed, 05 May 2021 07:32:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1leC14-0004Tx-SS for pgsql-docs@arkaria.postgresql.org; Wed, 05 May 2021 07:32:18 +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 1leC14-0004Tp-M3 for pgsql-docs@lists.postgresql.org; Wed, 05 May 2021 07:32:18 +0000 Received: from mail-wm1-x336.google.com ([2a00:1450:4864:20::336]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1leC12-0003k2-LP for pgsql-docs@lists.postgresql.org; Wed, 05 May 2021 07:32:18 +0000 Received: by mail-wm1-x336.google.com with SMTP id j3-20020a05600c4843b02901484662c4ebso2803409wmo.0 for ; Wed, 05 May 2021 00:32:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=3TVj88VZvCjxE3bAgqFQJiVcdq3ImSNpfQaxcL+UNwY=; b=UlTIGVJ8NElE84hp7l0hFLBwzbo7x6x8kqnX3/fxCcjDrm1GCX/sPOaN460CQT/6qS p8S2UJneZQElgQodPdWtdteeJ9qo6yI7al2RorLL46fZagvYJip603yDEr7VCxJuh0aJ qeX/tjDlj+i9a+mRO1u+1n86y01TAbckqmBcmL/WKOIIhwJ4/XBnHobm8zfQT2OP3bcS ivDOz9PGwKOsCaYHRIVshcofIpqmoMsuhPuHEtLQbKJ+BcvP+wK1/SZ+d61KeQZ/FD7X 7hu9Re+geQ14Q3Ec1LZUkUlKOfeJ66tsP/86Kk/QU6UQ0u7mJ1ACCiKb5gSsTfsEvCJh qejA== 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:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=3TVj88VZvCjxE3bAgqFQJiVcdq3ImSNpfQaxcL+UNwY=; b=tMU5Y6etQ1GUljjbr8eeAJFagCtfvwr4Nhn/TGx5c+x75v7Mu1vrEEfyobRiGKeJC2 0hXxcoMPmArDhx4o65b8g/wdyMLZaKAsJLY2Ql/GYTIJZWJ8kYYwUfdG+J0ZKCMJVlK5 ldw40mkDd+FuoBvb+7xXSSeo7PtZfBnpNXvieqPuKYTEoLw7ldTOZ0nrUI3wbjhT0OtQ 5Ym+eIWWUgxa98cE1s3yg2pmJKIZ+GnuhZRyFwygzqkFxCHmoNARXjI6s6YNWYaRE6Yq IFCDvj5X3AsjV2fPwUtvoSSazpiPW+rAuazgnbCKs8x0oeqt+M2q+n1uoau8hgVyFHQH 0oQg== X-Gm-Message-State: AOAM532NRqVJ1zF5AuA/DebSscaR0lcQE7p6b3nxvb8ghuk3DInex/Vf gvkhHeLUGsAU+JMH03XhuweTVw== X-Google-Smtp-Source: ABdhPJxXfieFaLHLmZtXXZXrfCZSBfPoU3Ur+I4SdgVfYGZbRTxLezlqRkLOPZUV+o7mnpp0IgczuA== X-Received: by 2002:a7b:c206:: with SMTP id x6mr8248222wmi.72.1620199934979; Wed, 05 May 2021 00:32:14 -0700 (PDT) Received: from localhost.localdomain (217-149-168-22.nat.highway.telekom.at. [217.149.168.22]) by smtp.gmail.com with ESMTPSA id l12sm18167439wrm.76.2021.05.05.00.32.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 05 May 2021 00:32:14 -0700 (PDT) Message-ID: <41d84eb3471bd6f42384f054c04573ad5c8d7aac.camel@cybertec.at> Subject: Re: BUG #16991: regclass is not case sensitive causing "relation does not exist" error From: Laurenz Albe To: Tom Lane , Federico Cc: pgsql-docs@lists.postgresql.org Date: Wed, 05 May 2021 09:32:14 +0200 In-Reply-To: <3976561.1620170328@sss.pgh.pa.us> References: <16991-bcaeaafa17e0a723@postgresql.org> <3896142.1620136761@sss.pgh.pa.us> <3904665.1620138892@sss.pgh.pa.us> <3976561.1620170328@sss.pgh.pa.us> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2021-05-04 at 19:18 -0400, Tom Lane wrote: > [ redirecting to pgsql-docs list ] > > I wrote: > > Federico writes: > > > I did not come across that documented behavior while searching for regclass > > > in the pg docs. The most relevant page I was able to find was the Object > > > Identifier Types page that does not mention it. > > > I'll look into proposing a change in that docs page to mention it, if > > > that's the appropriate location for it. > > Hmm ... I *thought* it was documented, but perhaps not. If not, > > it's likely that the other reg* types are likewise underdocumented. > > So what I was remembering was some text in the section about sequence > functions. That probably seemed appropriate when they were the only > real use of regclass; but these days we have regclass-accepting functions > all over, not to mention other OID alias types. I propose the attached > patch to move this info into the "Object Identifier Types" section. That patch looks good to me. I think it is an improvement to have that discussed under "data types". Yours, Laurenz Albe