| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:12:28 |
| Message-ID: | 20140829171228.GG7705@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Greg Stark <stark(at)mit(dot)edu> writes:
> > And I think there are still unanswered questions about indexes.
>
> 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.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-08-29 17:15:16 | Re: On partitioning |
| Previous Message | Tom Lane | 2014-08-29 16:52:22 | Re: On partitioning |