Benny,
I thought this might be one you might be interested in working on, too,
if you have time.
You could validate the update statement in pgxc_planner() if it is on a
partitioned table.
Thanks,
Mason
-------- Original Message --------
Subject: [ postgres-xc-Bugs-3107683 ] UPDATE on partition column
Date: Fri, 12 Nov 2010 02:29:56 +0000
From: SourceForge.net <no...@so...>
To: no...@so...
Bugs item #3107683, was opened at 2010-11-11 21:29
Message generated for change (Tracker Item Submitted) made by mason_s
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database Server
Group: None
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: mason_s (mason_s)
Assigned to: Nobody/Anonymous (nobody)
Summary: UPDATE on partition column
Initial Comment:
Until we support moving tuples from one node to another when the partition column of a table is updated, we should at least block this from happening. At the moment you can update it, and bad things can start happening as a result.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1310232&aid=3107683&group_id=311227
|
