Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
From: 0x0FFF <git@git.apache.org>
To: dev@hawq.incubator.apache.org
Reply-To: dev@hawq.incubator.apache.org
References: <git-pr-323-incubator-hawq@git.apache.org>
In-Reply-To: <git-pr-323-incubator-hawq@git.apache.org>
Subject: [GitHub] incubator-hawq pull request: [HAWQ-19] Money type overflow
 fixed b...
Content-Type: text/plain
Message-Id: <20160203082646.118D3DFC8F@git1-us-west.apache.org>
Date: Wed,  3 Feb 2016 08:26:46 +0000 (UTC)

Github user 0x0FFF commented on the pull request:

    https://github.com/apache/incubator-hawq/pull/323#issuecomment-179084818
  
    Speaking about this specific case: do we plan an upgrade path from HAWQ 1.x to 2.0? If no, then this PR can be easily merged into 2.0. If yes, we should really care about the upgrade path, and maybe the better solution here would be the following: instead of changing existing data type introduce new one, like "money8" for 8-byte money data type. This would again be a catalog change (for example, in pg_type), but still won't affect the customers using old data type "money" and layout of their existing tables
    
    Generally speaking, I agree that this is a tough question. Postgres is not a very good example here - you can easily do pg_dump and pg_restore there as the data volumes it operates with are usually quite small. As of HAWQ, making dump and restore to accommodate storage format change can't be an option as we might have hundreds of TB there.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---