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 1ps8lu-0000I3-0f for pgsql-general@arkaria.postgresql.org; Thu, 27 Apr 2023 21:03:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ps8kt-0000Iu-An for pgsql-general@arkaria.postgresql.org; Thu, 27 Apr 2023 21:02:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ps8ks-0000Il-WF for pgsql-general@lists.postgresql.org; Thu, 27 Apr 2023 21:02:19 +0000 Received: from mail-pf1-x435.google.com ([2607:f8b0:4864:20::435]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ps8kp-002EiA-8E for pgsql-general@lists.postgresql.org; Thu, 27 Apr 2023 21:02:17 +0000 Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-63b733fd00bso7047404b3a.0 for ; Thu, 27 Apr 2023 14:02:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682629333; x=1685221333; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=zG23jIKBttWRQyAQn/O+T/fFa+e3IlQwcLm+nF96zT8=; b=OASfP56eDUpaW5zNtno4BLtkhSzJDTURlf8rWlj2arr7haZROczgDaMrSu0qf60CJd FLULO2X4j6wYRY+sdU1al4TiG+UFrYh73FxZDNwQWFG/jhaidYLlD4Qc075Os4lA25l7 teH9d+JCIbcw2HncVdLJTBlYEKXJY9FOzomLDFgazcS4IEDZltmSCKoGp8Dzf67FAcCv QL6nO51NFJh+hBYp1b7WNeS/AnF5GKzORbsn9xU9spyjTijEpiMxaa/qXXQ6xtHfDZ1C TTTFb5CceTKoq9f+h6Oz2cASpu+ah7Ir89cb0+mdukoeMbkntI1QD1lwe5eA2jWyOWkx Jnzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682629333; x=1685221333; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=zG23jIKBttWRQyAQn/O+T/fFa+e3IlQwcLm+nF96zT8=; b=d3DfRS2L6hvNH6hLZM5LTs5KEQq++wX7CqccpcmZrCZuf/w9Hqo2rKBFaNLo55B5N9 LzeaiNN7s0p5c+w4b/vX8Znra2dIF39a1//+i5HFhNI3l37+CvJNPYQsLXiY8IiABMbX mjWJ4kKfgEmbfGNexvwe8gzHMpCRsvHxOo8+XuHo/gwiWnDVqIlW+4jiEWrw3otFNMsq pp6J3Rj6VYiXF+89ezqZ6f6T7smIIAdd6OWI4zIr9NTWK5prt9fZq4YaaNemg0d4292V RvQFU+W+THx7YuQNRtgcYD3ydIUUzfp/uR0ZF4nCR+5FM0eCYVx8iRqt1MUJcSaHwALI 9Pcg== X-Gm-Message-State: AC+VfDzCGD7nKm6hqtSzQGnQVM5lG32VGqJYQw8sOLndw1gYtwB91HKc ejKZe2tmJZEc9pYvPWhB9z1zKWqmRR8= X-Google-Smtp-Source: ACHHUZ48hDlVCSDsbJU2qCNTT6/ilg6lh8odTT09YwXskbfN5yJ94BGKT6OT4umPkCCDDgloEyJBKQ== X-Received: by 2002:a17:90a:f312:b0:24c:1cc:e15 with SMTP id ca18-20020a17090af31200b0024c01cc0e15mr3342417pjb.12.1682629333226; Thu, 27 Apr 2023 14:02:13 -0700 (PDT) Received: from smtpclient.apple ([199.117.84.110]) by smtp.gmail.com with ESMTPSA id ev10-20020a17090aeaca00b0024b79a69361sm9677100pjb.32.2023.04.27.14.02.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Apr 2023 14:02:12 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-6AD24CF4-3204-4F87-9FBA-B47BDD0D68BE Content-Transfer-Encoding: 7bit From: Rob Sargent Mime-Version: 1.0 (1.0) Subject: Re: Postgres query doesn't accept double quote around schema name in query statement Date: Thu, 27 Apr 2023 14:02:01 -0700 Message-Id: <6FAB6C86-6041-4105-96F0-DA27448B2615@gmail.com> References: Cc: pgsql-general@lists.postgresql.org In-Reply-To: To: Michael Xu X-Mailer: iPhone Mail (20E252) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail-6AD24CF4-3204-4F87-9FBA-B47BDD0D68BE Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Apr 27, 2023, at 12:40 PM, Michael Xu wrote: >=20 > =EF=BB=BF > Hi, >=20 > By default, pgsql accepts double quotes around schema's name in a query, e= .g. select * from "ads"."MyTableName". In our env, it throws 42P01:relation "= ads.MyTableName" does not exist. It is okay if no double quote around schema= name, select * from ads."MyTableName".=20 >=20 > Is there settings in pssql server or db level to change it back to its def= ault to allow double quotes around schema.=20 >=20 > We're using PostgreSQL 13.7 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8= .5.0 20210514 (Red Hat 8.5.0-10), 64-bit=20 >=20 > Thanks! >=20 > Michael >=20 Any chance the actual name of the schema is not all lowercase ads? --Apple-Mail-6AD24CF4-3204-4F87-9FBA-B47BDD0D68BE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

On Apr 27, 2023, at 12= :40 PM, Michael Xu <online.mxu@gmail.com> wrote:

<= /div>
=EF=BB=BF
Hi,=

By default, pgsql accepts double quotes around schema's n= ame in a query, e.g. select * from "ads"."MyTableName". In our env, it throw= s 42P01:relation "ads.MyTableName" does not exist. It is okay if no double q= uote around schema name, select * from ads."MyTableName". 

Is there settings in pssql server or db level to change it back t= o its default to allow double quotes around schema. 

We're using PostgreSQL= 13.7 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10), 64-bit 


Thanks!


Micha= el



Any chance the actual name of the schema is not a= ll lowercase ads?


= --Apple-Mail-6AD24CF4-3204-4F87-9FBA-B47BDD0D68BE--