Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eglFm-0005x8-7F for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Jan 2018 05:48:14 +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 1eglFj-0001Wn-OX for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Jan 2018 05:48:11 +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 1eglFj-0001Wd-F8 for pgsql-hackers@lists.postgresql.org; Wed, 31 Jan 2018 05:48:11 +0000 Received: from mail-lf0-x232.google.com ([2a00:1450:4010:c07::232]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eglFa-0005fw-H9 for pgsql-hackers@postgresql.org; Wed, 31 Jan 2018 05:48:10 +0000 Received: by mail-lf0-x232.google.com with SMTP id f136so18850259lff.8 for ; Tue, 30 Jan 2018 21:48:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language; bh=VDS6+3fNulhJhirKDLOUsRdw4TAzONgygIYVhDam4xc=; b=dsB60f2w1eGHuRa6U7r00Pqdvgd4RfCorw4Ojvhed4JZwXSHaHGhY/VK4W0RhnuCG7 qaA/1E1SBrEe4lzSB7m1d180oKXwFH9GJBZwcjmw6hRvXJ7LZ5LOCPER7aWaUmwQFhy1 17oDpPMV0vAAyiuT3oA3jM5pz4ZGJRJCMJviAQY/7m0GnjqodYgNaGJpSvrFY3sajMxL hJFgTJgmY2IDhn2k8SGXDDfYN+k6haZkU/dJ3Tb/haGOwiC8JdJHuowQPqYBa5kHzYdm aLTJJ4jcpZjZ01+2R54bM3d552diQaA7oVAWuwMn3zcWiAn8xaYG2yKR58Kyp9qSvJc5 Szsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language; bh=VDS6+3fNulhJhirKDLOUsRdw4TAzONgygIYVhDam4xc=; b=VUUMA05CxuBxb0LfBldnGblClYdGkxYfX9HAXdJB6DnijLcaWtXIoj5tNJ5qWmhlAH 4bQDJRHOXAiU8yjQ6PwGHMPuUQWYBpBBgLQh6Vg48etRTIC6VtIGidiIHbmCiduvEsuk o+mOk5a7f4HoJBeCHlkGScvk9pU0pQLgNviJOpRCSUSMXGLeybvs+BrwvWIjmzXu/Z3S 3SpWlDkc/HNr/YjrsOm/Svqh02YMB3XxHrJMCwAaCZhUMb20+wdztdYu8p5toWUU7Rw+ YN4Rd5ivYUKZAKZIgijGce7jJdR0tkSMxMfmlTcCZaPqEStPdkbW5U8SC+fcab1pLcRh 2Qlw== X-Gm-Message-State: AKwxyteaXK+TCjOb7Vw0ME/jYSgmoTWd2zXhu2TBCNS7zaCdgGglrm2I zCXzoE7fZEZlpQLSar5QCa2q+A== X-Google-Smtp-Source: AH8x227fzUGoNwcegnhDeDFebmWPPiZMV6Gl3iUGW/B/gH5MpJEU2ufGkrsR86QSAUc1rRtihS2f9g== X-Received: by 10.25.196.8 with SMTP id u8mr16469238lff.108.1517377680173; Tue, 30 Jan 2018 21:48:00 -0800 (PST) Received: from [1.0.0.7] ([178.155.4.116]) by smtp.gmail.com with ESMTPSA id y198sm3650226lfd.62.2018.01.30.21.47.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jan 2018 21:47:58 -0800 (PST) To: pgsql-hackers From: Alexander Lakhin Subject: A typo in error message Message-ID: <45c44aa7-7cfa-7f3b-83fd-d8300677fdda@gmail.com> Date: Wed, 31 Jan 2018 08:47:57 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------78403CD48ECD51B665BA4122" Content-Language: ru-RU List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------78403CD48ECD51B665BA4122 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello, Please consider committing the attached patch to fix a typo in error message. Best regards, -- Alexander Lakhin Postgres Professional: http://www.postgrespro.com The Russian Postgres Company --------------78403CD48ECD51B665BA4122 Content-Type: text/x-patch; name="colums.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="colums.patch" diff --git a/src/backend/parser/parse_utilcmd.c b/src/backend/parser/parse_utilcmd.c index e0d96d7..4894812 100644 --- a/src/backend/parser/parse_utilcmd.c +++ b/src/backend/parser/parse_utilcmd.c @@ -668,7 +668,7 @@ transformColumnDefinition(CreateStmtContext *cxt, ColumnDef *column) if (cxt->ofType) ereport(ERROR, (errcode(ERRCODE_FEATURE_NOT_SUPPORTED), - errmsg("identity colums are not supported on typed tables"))); + errmsg("identity columns are not supported on typed tables"))); if (cxt->partbound) ereport(ERROR, (errcode(ERRCODE_FEATURE_NOT_SUPPORTED), diff --git a/src/test/regress/expected/identity.out b/src/test/regress/expected/identity.out index 87ef0d3..627389b 100644 --- a/src/test/regress/expected/identity.out +++ b/src/test/regress/expected/identity.out @@ -349,7 +349,7 @@ DROP USER regress_user1; -- typed tables (currently not supported) CREATE TYPE itest_type AS (f1 integer, f2 text, f3 bigint); CREATE TABLE itest12 OF itest_type (f1 WITH OPTIONS GENERATED ALWAYS AS IDENTITY); -- error -ERROR: identity colums are not supported on typed tables +ERROR: identity columns are not supported on typed tables DROP TYPE itest_type CASCADE; -- table partitions (currently not supported) CREATE TABLE itest_parent (f1 date NOT NULL, f2 text, f3 bigint) PARTITION BY RANGE (f1); --------------78403CD48ECD51B665BA4122--