Re: ATTACH/DETACH PARTITION CONCURRENTLY

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ATTACH/DETACH PARTITION CONCURRENTLY
Date: 2018-11-06 19:01:09
Message-ID: CANP8+jLwYf42kh+=sutV1KRm1HupV0-WPX1wT44wtVzZc6L7Lw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 6 Nov 2018 at 10:56, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Tue, Nov 6, 2018 at 1:54 PM Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> > Error in the COPY or in the DDL? COPY preferred. Somebody with insert
> rights shouldn't be able to prevent a table-owner level action. People
> normally drop partitions to save space, so it could be annoying if that was
> interrupted.
>
> Yeah, the COPY.
>
> > Supporting parallel query shouldn't make other cases more difficult from
> a behavioral perspective just to avoid the ERROR. The ERROR sounds
> annoying, but not sure how annoying avoiding it would be.
>
> In my view, it's not just a question of it being annoying, but of
> whether anything else is even sensible. I mean, you can avoid an
> error when a user types SELECT 1/0 by returning NULL or 42, but that's
> not usually how we roll around here.
>

If you can remove the ERROR without any other adverse effects, that sounds
great.

Please let us know what, if any, adverse effects would be caused so we can
discuss. Thanks

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-11-06 19:05:57 Re: ATTACH/DETACH PARTITION CONCURRENTLY
Previous Message Tom Lane 2018-11-06 19:00:14 Re: Optimizing nested ConvertRowtypeExpr execution