Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eadDD-0000Ym-Iq for pgsql-docs@arkaria.postgresql.org; Sun, 14 Jan 2018 08:00:15 +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 1eadDB-0003VG-TF for pgsql-docs@arkaria.postgresql.org; Sun, 14 Jan 2018 08:00:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eadDB-0003Ut-Kl for pgsql-docs@lists.postgresql.org; Sun, 14 Jan 2018 08:00:13 +0000 Received: from mail-pg0-x241.google.com ([2607:f8b0:400e:c05::241]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eadD8-0006YA-17 for pgsql-docs@postgresql.org; Sun, 14 Jan 2018 08:00:12 +0000 Received: by mail-pg0-x241.google.com with SMTP id d6so6710717pgv.2 for ; Sun, 14 Jan 2018 00:00:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=uutGd4jiBuvS2fcPewgqVkLJsFpv5d3UNVamEw3ails=; b=JVg2W3IGZ7/yG9LSfR7IZmgQpUAH3cw7PX5ucIu3L2NIan6QY9PxsJjSFi34DZexXU LCfLUtJ0qV0Hoza7hm2iGqbGw+wm7QMCGYylNEkf9JFEdHcgN5SpTDxPqxgKd+uE455t eUAw41qhGVKjDW+gxlm4U2HDObyYUJbK3JWkuG1b08S5tn6xtcyrwuDc5ZT+JvKD9aIj 0zGH6m9UYdwNz9o6VrGzdQYGWCDibrpuaEkmtFWnvjI9LbGaSy6IdBBahJhDKeF4TBvm YOYhQktddIlIU2xCA3ybg+0sxii9OCxbye6A3fjv0o7CZr1VP/pxs6I7mRWEJcxIDfek FGWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=uutGd4jiBuvS2fcPewgqVkLJsFpv5d3UNVamEw3ails=; b=a7BjIC/bv3SVVTqHx2zNN1JYAQCG5YptyU9HaKNyYeAcNuJTjwG5sfYOrMl4Pkw36V bmZKzoHeozk20UhhpUwDgLpr+E0nuwuM1bA4MuHLGSX7X8ev0inCXms2Dt69PhFzS6Za UBaRtZh/kvLz0bl2yFaCQNOBJy2kt7E1tD1giEBip6DYpbZRd8PtKEojWM8pNO0ADRCW 8GV7ZrF8GaZ9vlC9futG6jSlFtT2YPgRmh1ZCzJPDnChddxbQ9+Yo+jNkOu35MpomLhF BB3OoaQab8pcf6WOhy+cbXzL6Y48jtBTE40+GShF8bez/WIefjHgy6jB/bi6DqVCdXF5 Mk0w== X-Gm-Message-State: AKGB3mKWynUfXUeJZsviHDEjfZppyabRw8Pq5uxz0MYxGSNL88ghSeBs NvSmpK59MJEx2MaAi3uZOHU= X-Google-Smtp-Source: ACJfBov+JUrDZaQvQ2q1/hwFfG7ImAR7FMJcEqRV2VfQuJJPo5cBUO35rAYG5tEqTYFj/O1SuO+ycg== X-Received: by 10.101.88.206 with SMTP id e14mr15929788pgu.441.1515916806654; Sun, 14 Jan 2018 00:00:06 -0800 (PST) Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp. [61.215.137.162]) by smtp.gmail.com with ESMTPSA id m9sm3336345pff.59.2018.01.14.00.00.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 14 Jan 2018 00:00:05 -0800 (PST) Date: Sun, 14 Jan 2018 17:00:01 +0900 From: Michael Paquier To: Stephen Frost Cc: lampacz@gmail.com, pgsql-docs@postgresql.org Subject: Re: Missing column_constraint explanation Message-ID: <20180114080001.GA1045@paquier.xyz> References: <20171220090816.25744.72592@wrigleys.postgresql.org> <20171221031511.GX4628@tamriel.snowman.net> <20180114020622.GO2416@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <20180114020622.GO2416@tamriel.snowman.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 13, 2018 at 09:06:22PM -0500, Stephen Frost wrote: > I'm not really sure that we want to go there for this case though. > Perhaps others disagree, but that seems like a lot to avoid this > particular duplication, which really isn't all that bad. >=20 > This patch also seems to have gotten lost in the shuffle of things, but > it still applies cleanly and I took another look at it today and it > looks good to me, so I'm going to stick it in the CF and mark it as > Needs Review for now. Perhaps someone else can give it another > once-over to make sure everything looks good and, if so, mark it as > Ready for Committer and then I'll take care of it. I may be missing something, but no patch is attached to this thread. Honestly I think that duplicating this code should be avoided, and the patch to produce is not that complicated technically. So are you planning to just duplicate hte definitions in CREATE TABLE to ALTER TABLE? This is a recipy for forgetting updates in the future on one page or the other... -- Michael --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlpbDgEACgkQnvQgOdby QH0MJhAAgmyR5XzPBrUKHE8vUdRAKBtv7G+Dk5wdfRaNW3+I84OQzQeQVnysfNjh IX8wiFxm/mFUax7G0dB0DA3k/0gKDtihuxex3/VSrd1UnNogG+nMb/PN8+k9xwsA QJeNANuRh+0SsNUkKDRWZCLoxfivD1RSOPGYdjvKEELR9CreBN+bUiACsx/zFZVh gUvjALGjrfDB2AhdjU5vrU7p9nmaB3NKp5fleycvrUO8G2k0bmBUquH/6pNi24v6 oGklvP0ZfW4MbEsNd+S+SBmNqCmXtNxm3cryT6bjxc5jDPn1/dw/gMerqztb8CNP RJ4iI0QcFrJjvrEIJ56xM6NqmtHH0W4EvEOp3idkVfNCk14iYm/nv8TaLVbCC8m5 MV9m2q3ta0P88KGUE9yFtZwPgeYxEf6kktcKwEfv93s7AOUlKUhMucy47nv/vkgi tdSMd8FRtvFfVl9klJj3FDw1FpS8xLdt+1oCnKrR4oskx4KY/Q9Non4ZX7nqhCjC G0pv6SKFhK2lVJz+ZCq7AOJuPMxkXaUbbcuM496JS6OO2IzDUtcFD4dHlkTr2coP X+02sxzcWysOfch9u4iRIo3AnWWijafxQHITNNpoiCYTq4SmKN9zDFhwWy+Mtez3 EWiWTyuT0DLOXk+AYYsxTLJRYR96vXCaBJBKdDYsoUKeG5QlyOg= =o+Ph -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI--