| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | frimmelv(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org> |
| Subject: | Re: BUG #15937: Partitioning |
| Date: | 2019-08-02 09:25:59 |
| Message-ID: | e7881eb1-2a0a-12c0-b0bb-212248cb5d1b@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2019-08-05 05:55:55 | Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly |
| Previous Message | PG Bug reporting form | 2019-08-01 13:52:52 | BUG #15938: Corrupted WAL segment after crash recovery |