Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gSXrS-000735-0G for pgsql-docs@arkaria.postgresql.org; Fri, 30 Nov 2018 01:44:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gSXrQ-0008O9-Lw for pgsql-docs@arkaria.postgresql.org; Fri, 30 Nov 2018 01:44:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gSXrQ-0008O0-7s for pgsql-docs@lists.postgresql.org; Fri, 30 Nov 2018 01:44:52 +0000 Received: from mail-pf1-x435.google.com ([2607:f8b0:4864:20::435]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gSXrL-0001vu-KS for pgsql-docs@lists.postgresql.org; Fri, 30 Nov 2018 01:44:50 +0000 Received: by mail-pf1-x435.google.com with SMTP id c123so1969474pfb.0 for ; Thu, 29 Nov 2018 17:44:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=bvqi2HWUmcBZ9HXsxJeZL7ksWADzzo1Ur28OmOywCJI=; b=Vjf5pSYvok36ZRoBi+ShbeW7r3kLCu+wTvNWtxElK5NugT+pMB9FBC7ymY8+1WwLDy iyzlWxuFZWDPIZHXscUmNahDB28IEsv8ocy2G2/cK1DejDZ6bh7HqlbVeKm1EuAhzEGX ABsvhxkjSv0iXllrSTUQLgWpd9iygWaNJgeTH9fgF7qK1jBHGx74SZJ6K9jqV9u46eqU fAsLHrl7wJGNNEZPlh8Q+bY6QOfa5KkFYEcLxrpCzDTG7/mWNJF2KuYb7ZJxkpVVGk1H hxlkyOctf1IjVrXTygcTEZCgyLn/AauYFUYYdTIhch9f2QT+is/5ZKdBQuvz0krRJiU5 ykrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bvqi2HWUmcBZ9HXsxJeZL7ksWADzzo1Ur28OmOywCJI=; b=OmSB+7nvCfJoLcV/iGJ68z446LJqag/Jh2gzrA3MrS0vMwpnE3F9YOBxgeLmjQ7naT xM8Ide4PlC1VxD2j+fFdOrH7HzgGrbqrNbxqa59wX7y3rl8qm4D/Y/QcwLliGnwy9Xmg 9p249Tjk9ivuRU59GQx4kf+PjBq+bD433PfyxnJNupYhpEp5mXGcTaI3ajSIm2tfx7mu s8NRYxmlxrGrIeRh7vjymEZZNzptz6yVJbX3kb9IFe9S9ahos5vRdcPzZ3hpfw3hu8Xm gvEMRYshXe+tUd/QkodDWHduWnUcAv7bag5m6MA5alilQnZmKFfEjmjdJK0K7hA9WaIc mMKw== X-Gm-Message-State: AA+aEWahv7Bg0U+puzSQiJtIsHDfmOmGMDN39Dxxk8K4Tgwd7R08Lz2C yfwWQqlePGemqW0fi9HnQsxVqQ== X-Google-Smtp-Source: AFSGD/Up2EhWV0lPR6h70/UxNRPoKyRJi3c+1+XOrkpHTrcX8YzumNxiJbtTMpg0Y9pP2mAfS0+YFA== X-Received: by 2002:a62:3305:: with SMTP id z5mr3807171pfz.112.1543542285665; Thu, 29 Nov 2018 17:44:45 -0800 (PST) Received: from osaka.octopusnet (p6326108-ipngn31001marunouchi.tokyo.ocn.ne.jp. [153.174.20.108]) by smtp.gmail.com with ESMTPSA id r130sm5379630pfr.48.2018.11.29.17.44.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Nov 2018 17:44:44 -0800 (PST) Subject: Re: Objects without schema To: jobyjc@gmail.com, pgsql-docs@lists.postgresql.org, PG Doc comments form References: <154351247845.1315.1692288968604791039@wrigleys.postgresql.org> From: Ian Barwick Message-ID: <55aeb849-4cea-ef50-9076-db5703220548@2ndquadrant.com> Date: Fri, 30 Nov 2018 10:44:42 +0900 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <154351247845.1315.1692288968604791039@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 11/30/2018 02:27 AM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.5/ddl-schemas.html > Description: > > In the last section of the document it says 'If you need to work with those > systems, then maximum portability would be achieved by not using schemas at > all.'. > But how do we achieve this? If I am not mistaken, all objects(like tables) > created in the database need to be created under one schema. Correct, in that every object has to have a schema, by default the "public" schema. I suspect what this is trying to say is that you should keep all objects under one schema, and not explicitly reference that schema; that way queries and DDL would be more portable. Regards Ian Barwick -- Ian Barwick http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services