| From: | amul sul <sulamul(at)gmail(dot)com> |
|---|---|
| To: | alvherre(at)2ndquadrant(dot)com |
| Cc: | Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Multiple primary key on partition table? |
| Date: | 2018-10-05 04:50:45 |
| Message-ID: | CAAJ_b97=NGFsmhiK0EwdbRR1+FOFBSKvU=GkHNi0M8nXj2TfkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 4, 2018 at 8:25 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
> On 2018-Oct-01, Rajkumar Raghuwanshi wrote:
>
> > On Tue, Sep 18, 2018 at 11:20 AM amul sul <sulamul(at)gmail(dot)com> wrote:
> >
> > > Here is the complete patch proposes the aforesaid fix with regression test.
> >
> > Thanks, This worked for me.
>
> Yeah, looks good to me, pushed. I added one more regression test to
> ensure that the PRIMARY KEY clause in the partition is still accepted if
> the parent does not have one.
>
Thanks a lot, for enhancing regression and committing the fix.
Regards,
Amul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2018-10-05 05:21:42 | Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru |
| Previous Message | Michael Paquier | 2018-10-05 04:22:36 | Assertion failure with ALTER TABLE ATTACH PARTITION with log_min_messages >= DEBUG1 |