Re: ATTACH/DETACH PARTITION CONCURRENTLY - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ATTACH/DETACH PARTITION CONCURRENTLY
Date
Msg-id CA+TgmoYQAn6PdSQjPaiowZd+MxHT4PRG4Ny1iYLNAqLkg0KKSw@mail.gmail.com
Whole thread Raw
In response to Re: ATTACH/DETACH PARTITION CONCURRENTLY  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: ATTACH/DETACH PARTITION CONCURRENTLY  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Tue, Nov 6, 2018 at 1:54 PM Simon Riggs <simon@2ndquadrant.com> wrote:
> Error in the COPY or in the DDL? COPY preferred. Somebody with insert rights shouldn't be able to prevent a
table-ownerlevel 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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Jesper Pedersen
Date:
Subject: Re: Speeding up INSERTs and UPDATEs to partitioned tables
Next
From: Tom Lane
Date:
Subject: Re: Optimizing nested ConvertRowtypeExpr execution