Re: Getting ERROR: could not open file "base/13164/t3_16388" with partition table with ON COMMIT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Getting ERROR: could not open file "base/13164/t3_16388" with partition table with ON COMMIT
Date
Msg-id 10741.1536848021@sss.pgh.pa.us
Whole thread Raw
In response to Re: Getting ERROR: could not open file "base/13164/t3_16388" withpartition table with ON COMMIT  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: Getting ERROR: could not open file "base/13164/t3_16388" withpartition table with ON COMMIT  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> writes:
> On 2018/09/13 1:14, Tom Lane wrote:
>> That seems excessively restrictive.  Anything that has storage (e.g.
>> matviews) ought to be truncatable, no?

> Not by heap_truncate it seems.  The header comment of heap_truncate says
> that it concerns itself only with ON COMMIT truncation of temporary tables:

Ah.  Well, in that case I'm OK with just a simple test for
RELKIND_RELATION, but I definitely feel that it should be inside
heap_truncate.  Callers don't need to know about the limited scope
of what that does.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Avoid extra Sort nodes between WindowAggs when sorting can be reused
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Cutting initdb's runtime (Perl question embedded)