Re: Getting ERROR with FOR UPDATE/SHARE for partitioned table.

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: amul sul <sulamul(at)gmail(dot)com>
Cc: Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Getting ERROR with FOR UPDATE/SHARE for partitioned table.
Date: 2020-05-28 10:31:37
Message-ID: CA+HiwqHhC4P8TSch=keRukdrL3vQ53WtGN6ik9R0zUmffA-q+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 28, 2020 at 1:36 PM amul sul <sulamul(at)gmail(dot)com> wrote:
> On Wed, May 27, 2020 at 12:53 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
>> I guess the workaround is to declare the cursor such that no
>> partitions/children are pruned/excluded.
>
> Disabling pruning as well -- at-least for the statement or function.

Now *that* is actually a workaround to tell a customer. :)

--
Amit Langote
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2020-05-28 11:12:29 Re: WIP: WAL prefetch (another approach)
Previous Message Dilip Kumar 2020-05-28 10:12:23 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions