From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Greg Stark <stark(at)mit(dot)edu>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: On partitioning |
Date: | 2014-08-29 17:15:16 |
Message-ID: | 21834.1409332516@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Tom Lane wrote:
>> One other interesting thought that occurs to me: are we going to support
>> UPDATEs that cause a row to belong to a different partition? If so, how
>> are we going to handle the update chain links?
> Bah, I didn't mention it? My current thinking is that it would be
> disallowed; if you have chosen your partitioning key well enough it
> shouldn't be necessary. As a workaround you can always DELETE/INSERT.
> Maybe we can allow it later, but for a first cut this seems more than
> good enough.
Hm. I certainly agree that it's a case that could be disallowed for a
first cut, but it'd be nice to have some clue about how we might allow it
eventually.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-08-29 17:22:16 | Re: On partitioning |
Previous Message | Alvaro Herrera | 2014-08-29 17:12:28 | Re: On partitioning |