| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> |
| Subject: | Re: Broken defenses against dropping a partitioning column |
| Date: | 2019-07-08 15:03:23 |
| Message-ID: | CA+TgmoZ7cpTkKsFBun14QhAQ53H_Qi1_vxea=TAG34s=JnPc4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 8, 2019 at 11:02 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Jul 8, 2019 at 10:32 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> > That said, I'm not sure I see the use case for an ALTER TABLE .. DROP
> > COLUMN command that turns a partitioned table (with existing partitions
> > containing data) into one non-partitioned table with all data minus the
> > partitioning column(s).
>
> I think it would be useful to have "ALTER TABLE blah NOT PARTITIONED" but I
...hit send too soon, and also, I don't think anyone will be very
happy if they get that behavior as a side effect of a DROP statement,
mostly because it could take an extremely long time to execute.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-07-08 15:07:59 | Re: Broken defenses against dropping a partitioning column |
| Previous Message | Robert Haas | 2019-07-08 15:02:36 | Re: Broken defenses against dropping a partitioning column |