| From: | Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UPDATE of partition key |
| Date: | 2017-05-03 05:52:21 |
| Message-ID: | CAJ3gD9c04=uoswh93W6E43-CshsgALzkzhPDLNMk-NjeqZN5Nw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2 May 2017 at 18:17, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Apr 4, 2017 at 7:11 AM, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> wrote:
>> Attached updated patch v7 has the above changes.
>
> This no longer applies. Please rebase.
Thanks Robert for informing about this.
My patch has a separate function for emitting error message when a
partition constraint fails. And, the recent commit c0a8ae7be3 has
changes to correct the way the tuple is formed for displaying in the
error message. Hence there were some code-level conflicts.
Attached is the rebased patch, which resolves the above conflicts.
| Attachment | Content-Type | Size |
|---|---|---|
| update-partition-key_v7_rebased.patch | application/octet-stream | 32.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2017-05-03 06:10:16 | Re: Inefficient shutdown of pg_basebackup |
| Previous Message | Petr Jelinek | 2017-05-03 05:26:21 | Re: Concurrent ALTER SEQUENCE RESTART Regression |