From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgrowlocks relkind check |
Date: | 2017-06-13 13:53:45 |
Message-ID: | bb3d9024-ba7e-a06e-b619-d9933ceb9168@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/12/17 21:10, Amit Langote wrote:
> On 2017/06/13 0:29, Peter Eisentraut wrote:
>> On 4/24/17 21:22, Amit Langote wrote:
>>>>> create extension pgrowlocks;
>>>>> create view one as select 1;
>>>>> select pgrowlocks('one');
>>>>> -- ERROR: could not open file "base/68730/68748": No such file or directory
>>>>>
>>>>> With the attached patch:
>>>>>
>>>>> select pgrowlocks('one');
>>>>> ERROR: "one" is not a table, index, materialized view, sequence, or TOAST
>>>>> table
> FWIW, patch seems simple enough to be committed into 10, unless I am
> missing something.
>
> Rebased one attached.
According to CheckValidRowMarkRel() in execMain.c, we don't allow row
locking in sequences, toast tables, and materialized views. This is not
quite the same as what your patch wants to do. I suppose we could still
allow reading the relation, and it won't ever show anything
interesting. What do you think?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-06-13 14:05:07 | Re: RTE_NAMEDTUPLESTORE, enrtuples and comments |
Previous Message | Rahila Syed | 2017-06-13 13:44:12 | Re: Dropping partitioned table drops a previously detached partition |