Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dUfTt-0004y5-44 for pgsql-docs@arkaria.postgresql.org; Mon, 10 Jul 2017 20:40:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dUfTs-0000Ea-IL for pgsql-docs@arkaria.postgresql.org; Mon, 10 Jul 2017 20:40:32 +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 1dUfTr-0000Dr-Qv for pgsql-docs@postgresql.org; Mon, 10 Jul 2017 20:40:31 +0000 Received: from pb-smtp1.pobox.com ([64.147.108.70] helo=sasl.smtp.pobox.com) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dUfTo-00046i-20 for pgsql-docs@postgresql.org; Mon, 10 Jul 2017 20:40:31 +0000 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 3D7AB84E9D for ; Mon, 10 Jul 2017 16:40:24 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:to; s=sasl; bh=ChsvvyRKTQSi7oUX0A4ycmnpmsg=; b= owh5M4Y0Ums/IyLJcp5eV0/+/fsZ3fHRoID3pztCMJIbddtze76lwt6hjGQ3pBEn bamVsisGsVjNGUYHzir5CpD9VP78n4Os+7dvxqsWXvCVHwdZ5jElutmoAqcoYLaX pEvnXjuCgcm2PiMQ6ahRIcMCW/U9i/75XwKMIX6SBnE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:to; q=dns; s=sasl; b=Kk+lKhc+63l6rKOzxALoQn76C4 oPGR64G7wYGb8vbdAgQy/mv4xZ6TZ+ne1vuEEAro/DxUHAdVW2Wxy6YsDtsjhO9q doVkv/HHO9OjFXUYrKlX28BqCpajLv6ZYUDr4vB15mMoS9Joom7FxzN5p9SmmY4E 174zDlbblC5M9YNMk= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 348A284E9C for ; Mon, 10 Jul 2017 16:40:24 -0400 (EDT) Received: from [192.168.7.176] (unknown [50.78.161.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 99D7984E9B for ; Mon, 10 Jul 2017 16:40:23 -0400 (EDT) From: Basil Bourque Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: =?utf-8?Q?Mention_new_=60GENERATED_=E2=80=A6_AS_IDENTITY=60_featu?= =?utf-8?Q?re_in_the_=60Serial_Types=60_page_=3F?= Message-Id: <7637CE20-AA33-48C4-AEBA-A0F591F87235@pobox.com> Date: Mon, 10 Jul 2017 13:40:24 -0700 To: pgsql-docs@postgresql.org X-Mailer: Apple Mail (2.3273) X-Pobox-Relay-ID: FF712750-65AF-11E7-BDAB-EFB41968708C-02729985!pb-smtp1.pobox.com List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org I suggest adding a mention of `GENERATED =E2=80=A6 AS IDENTITY` as a replac= ement for `SERIAL` in the =E2=80=9CSerial Types=E2=80=9D section 8.1.4 of t= he =E2=80=9CData Types=E2=80=9D page. https://www.postgresql.org/docs/devel/static/datatype-numeric.html#datatype= -serial Postgres 10 sports a new `GENERATED =E2=80=A6 AS IDENTITY` for an identity = column to effectively replace the `SERIAL` pseudo-type. See =E2=80=9CPostgreSQL 10 identity columns explained=E2=80=9D post for a d= iscussion of the various issues that plague `SERIAL` but not identity colum= ns. https://blog.2ndquadrant.com/postgresql-10-identity-columns/ Seems a shame to let the na=C3=AFve reader continue using `SERIAL` without = knowing about identity column feature. =E2=80=94Basil Bourque --=20 Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs