Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cbTJf-0001ML-8j for pgsql-sql@arkaria.postgresql.org; Wed, 08 Feb 2017 14:33:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cbTJd-0000tC-Sg for pgsql-sql@arkaria.postgresql.org; Wed, 08 Feb 2017 14:33:49 +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 1cbTIg-0008Es-60 for pgsql-sql@postgresql.org; Wed, 08 Feb 2017 14:32:50 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cbTIY-00070g-DV for pgsql-sql@postgresql.org; Wed, 08 Feb 2017 14:32:49 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 6E8A1208A2; Wed, 8 Feb 2017 09:32:40 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 08 Feb 2017 09:32:40 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=AQjPw/XuonLxnEl KGyHR57beqQ8=; b=YKiXHdBjHuRRkGxh8WuvQfuwK4XkXNPCWJRIK1gmxkJuB4C +Gd4LK5LCVBL/4pHWEUQ1XALBsjNyzreMJ6KIYCyYk/rGCo5y3t5TfR7ImkzTbOU Mz1rlSsCFxQlASCCHG540VcW4Tk4p1S9vb5Ru9zDcusekw3gUx2I+mdOC0is= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=AQjPw/XuonLxnElKGyHR57beqQ8=; b=omgWXCare27aSPW3aK8B aaIahgkgHCvt96s+as57VWbBUiyHt6LxxXu/8q2p16X4QI6baMb44AAqLls7Ah3k nIJ4evwL2cymzkLT7LKhk8K9IPxOmRCrkiqIPtesnW84HY/kdb/UW7un2l7nO8yN g39IMSlRp+pkz3lQKNaoft0= X-ME-Sender: X-Sasl-enc: HVnHOTpRJvuFdCFTkvOp2/sKvub+MJyUyc7Q1NojUmpo 1486564360 Received: from [192.168.1.2] (174-21-203-58.tukw.qwest.net [174.21.203.58]) by mail.messagingengine.com (Postfix) with ESMTPA id EB00C7E652; Wed, 8 Feb 2017 09:32:39 -0500 (EST) Subject: Re: Problem wil TIMEZONE vs TIME ZONE To: Mike Wes , pgsql-sql@postgresql.org References: From: Adrian Klaver Message-ID: <1ba442c9-98e2-c727-6933-8958617a7bdf@aklaver.com> Date: Wed, 8 Feb 2017 06:32:39 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org On 02/08/2017 03:20 AM, Mike Wes wrote: > Good day, > > Can anybody clarify the following behaviour of pgsql? A Windows user in > our project is not able to execute a create table command caused by the > timestamp field log_created using 'TIME ZONE' (giant_log2), but must > explict use 'TIMEZONE' (giant_log3). This is an issue while we use > liquibase in our project. Any ideas why this is happening? First some information is needed: 1) What version of Postgres is this being run against? 2) Where is the Postgres server located and how was it installed? 3) What is the error message from the failing CREATE TABLE statement? 4) How did the definition for giant_log2 become the definition for giant_log3 as they look like they came from different processes? > > > DROP TABLE IF EXISTS "public"."giant_log2"; > CREATE TABLE "public"."giant_log2" ( > "id" int8 NOT NULL, > "version" int8, > "uid" varchar(40) COLLATE "default", > "consumer_id" varchar(20) COLLATE "default", > "customer_id" varchar(20) COLLATE "default", > "provider_id" varchar(15) COLLATE "default", > "company_id" varchar(60) COLLATE "default", > "country_code" varchar(2) COLLATE "default", > "type_of_operation" varchar(40) COLLATE "default", > "log_created" timestamp WITH TIME ZONE, > "adapter_component" varchar(20) COLLATE "default", > "order_status" varchar(20) COLLATE "default", > "reference_nr" varchar(100) COLLATE "default", > "xml_data" text COLLATE "default" > ) > WITH (OIDS=FALSE); > ALTER TABLE "public"."giant_log2" OWNER TO "giant"; > > DROP TABLE IF EXISTS "public"."giant_log3"; > CREATE TABLE public.giant_log3 (id BIGINT NOT NULL, > version BIGINT, > uid VARCHAR(40), > consumer_id VARCHAR(20), > customer_id VARCHAR(20), > provider_id VARCHAR(15), > company_id VARCHAR(60), > country_code VARCHAR(2), > type_of_operation VARCHAR(40), > log_created TIMESTAMP WITH TIMEZONE, > adapter_component VARCHAR(20), > order_status VARCHAR(20), > reference_nr VARCHAR(100), > xml_data TEXT, > CONSTRAINT common_giant_log_pkey PRIMARY KEY (id)) > WITH (OIDS=FALSE); > ALTER TABLE "public"."giant_log3" OWNER TO "giant"; > > Kind regards, > > Mike > > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql