Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eRpD2-0004vR-C8 for pgsql-docs@arkaria.postgresql.org; Thu, 21 Dec 2017 00:59:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eRpD1-0005lA-RJ for pgsql-docs@arkaria.postgresql.org; Thu, 21 Dec 2017 00:59:39 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eRpD1-0005l0-FV for pgsql-docs@lists.postgresql.org; Thu, 21 Dec 2017 00:59:39 +0000 Received: from mail-wr0-f193.google.com ([209.85.128.193]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eRpCy-0007La-B0 for pgsql-docs@postgresql.org; Thu, 21 Dec 2017 00:59:37 +0000 Received: by mail-wr0-f193.google.com with SMTP id o2so23811367wro.5 for ; Wed, 20 Dec 2017 16:59:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=RmQM1gMw3sIf2n8wXVkds7OCTBJVKOILh0DZ1grxnRs=; b=IPjrwqf5cyr68PoGfrAmCqOLwguWzpV2nO4kGMsQvRkDhUNpQW3BtrAUbzTldTcncX W3+zHfJIOGqwwO3Sa/mmTXHT/N6NtuvMNyY0vRWNGAQnIAgvhFXeIQE9mWEm7+ZSJlvV wNAfCz8a6fYLlOfwnYc3P6A11dkqBYGPBfn5MieqOlFX6Pg54zeI+bpxXC5If4mOTSCS 47OAeBu0xvXxDI7fKD1gX32TH1WSw8zgpDzSiy+ejWnM5pcfQ+U0QvVnU4Ki2X8J/Q7X RwObrwhKz0VecAtJug4TzjfLDbPvDIKqdgyK7WIrPKESO7pequUgnMfql3SM+1wJPD+U gmlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=RmQM1gMw3sIf2n8wXVkds7OCTBJVKOILh0DZ1grxnRs=; b=M+vLwbQHLzBxda6IdZyTdyFFsJeGwIoKR7Wao91lugBF+WI0LTXG3noztN23Ksp1YJ /s1LskQRUZlTbUGeFSNOPnM/Z3vch5OBEcrmq/hPDBA9bcwWiu3jo53bt9hBAjri+mD9 XqwdtgdGBWqDujAXR4jsgcQn7HZ+RiQCiZwsdn/TPHKotXn/6FT/eYxGvsi7C0yQF9Es ZAjpcxBBUMQEoqu6+VcHiZ9GcZ1Xp9Bwv3balXLoF8qxEaq+KlUGEf3nYeP4b8xD4L51 RERPkFSZZ3Ksxkj+mTue+kKBdUdqGZwoPkD2IZbqM6qEbqhu6/h3qvy1bRH1kvGfeYBF EdKg== X-Gm-Message-State: AKGB3mLf8yVNL1UTNgBdaUkgYMDtihYzU5gA9HM3I7nTkhY2PLbRIHOC c1tCYTNlimr9UgWw2yx4dUPJx+ty1SwNZbbbwHc= X-Google-Smtp-Source: ACJfBotCfqdBw1Axn9KHYekPuMPqbrelB7VGwazkH9AjOfheNfsWCABsWun94yfqygX32CcjgP9l2eG6Oftcpn8oblI= X-Received: by 10.223.170.138 with SMTP id h10mr513084wrc.171.1513817914463; Wed, 20 Dec 2017 16:58:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.169.5 with HTTP; Wed, 20 Dec 2017 16:58:33 -0800 (PST) In-Reply-To: <20171220090816.25744.72592@wrigleys.postgresql.org> References: <20171220090816.25744.72592@wrigleys.postgresql.org> From: Michael Paquier Date: Thu, 21 Dec 2017 09:58:33 +0900 Message-ID: Subject: Re: Missing column_constraint explanation To: lampacz@gmail.com, pgsql-docs@postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Dec 20, 2017 at 6:08 PM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/sql-altertable.html > Description: > > Missing column_constraint explanation in parameters section Those docs say already that ADD COLUMN follows the same grammar as CREATE TABLE, which basically means that there is no need to duplicate the same definition in two places. Note that the same thing applies to table_constraint. -- Michael