| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UPDATE of partition key |
| Date: | 2017-05-17 11:47:51 |
| Message-ID: | CA+TgmoYqXHp92rXFQE=+UUQ9doz=o0XSt9DB7YGGZ=MiLfbWtQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 17, 2017 at 6:29 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> I think we can do this even without using an additional infomask bit.
> As suggested by Greg up thread, we can set InvalidBlockId in ctid to
> indicate such an update.
Hmm. How would that work?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-05-17 11:52:48 | Re: Increasing parallel workers at runtime |
| Previous Message | Masahiko Sawada | 2017-05-17 10:58:29 | Re: Get stuck when dropping a subscription during synchronizing table |