| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | amul sul <sulamul(at)gmail(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-09-24 15:57:12 |
| Message-ID: | 20180924155712.gm244rc2sheydmuf@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[Back from a week AFK ...]
On 2018-Sep-18, amul sul wrote:
> On Mon, Sep 17, 2018 at 9:06 PM amul sul <sulamul(at)gmail(dot)com> wrote:
> >
> > Nice catch Rajkumar.
> Here is the complete patch proposes the aforesaid fix with regression test.
Looks closely related to the one that was fixed in 1f8a3327a9db, but of
course it's a different code path. Will review this shortly, thanks.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-09-24 15:58:09 | Re: Segfault when creating partition with a primary key and sql_drop trigger exists |
| Previous Message | Michael Paquier | 2018-09-24 15:44:19 | Re: Revoke execution permission of pg_stat_statements_reset() from pg_read_all_stats role |