Re: Getting ERROR: could not open file "base/13164/t3_16388" with partition table with ON COMMIT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Getting ERROR: could not open file "base/13164/t3_16388" with partition table with ON COMMIT
Date: 2018-09-13 14:13:41
Message-ID: 10741.1536848021@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-09-13 14:18:49 Re: [HACKERS] Cutting initdb's runtime (Perl question embedded)
Previous Message Andrew Gierth 2018-09-13 14:04:10 Re: Avoid extra Sort nodes between WindowAggs when sorting can be reused