Re: BUG #15937: Partitioning - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #15937: Partitioning
Date
Msg-id e7881eb1-2a0a-12c0-b0bb-212248cb5d1b@2ndquadrant.com
Whole thread Raw
In response to BUG #15937: Partitioning  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On 2019-08-01 14:51, PG Bug reporting form wrote:
> Hi, is it possible to LOCK only PARTITION on partitioning table instead of
> whole TABLE?
> When I performed command LOCK with table partition name, no error raised,
> but whole table was locked. Is it OK? We need to lock onli partition, not
> whole table. This is the critical point in our migration from Oracle.

Can you show the actual commands of what you are doing?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15938: Corrupted WAL segment after crash recovery
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly