Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIcWt-0005gj-4m for pgsql-bugs@arkaria.postgresql.org; Wed, 16 Sep 2020 18:51:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kIcWr-0002kt-Of for pgsql-bugs@arkaria.postgresql.org; Wed, 16 Sep 2020 18:51:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIcWr-0002km-Iv for pgsql-bugs@lists.postgresql.org; Wed, 16 Sep 2020 18:51:41 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIcWp-0000AS-Br for pgsql-bugs@lists.postgresql.org; Wed, 16 Sep 2020 18:51:40 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 08GIpcZC1750082; Wed, 16 Sep 2020 14:51:38 -0400 From: Tom Lane To: Nagaraj Raj cc: "pgsql-bugs@lists.postgresql.org" Subject: Re: table partition with inheritance having current_timestamp issue if we miss range table In-reply-to: <280232870.3108583.1600280574763@mail.yahoo.com> References: <280232870.3108583.1600280574763.ref@mail.yahoo.com> <280232870.3108583.1600280574763@mail.yahoo.com> Comments: In-reply-to Nagaraj Raj message dated "Wed, 16 Sep 2020 18:22:54 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1750080.1600282298.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 16 Sep 2020 14:51:38 -0400 Message-ID: <1750081.1600282298@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Nagaraj Raj writes: > How to reproduce the issue, > 1.=C2=A0Create a=C2=A0table partition with table=C2=A0inheritance by ran= ge on the date column2. Place triggers and trigger function3. In the trigg= er function, update with=C2=A0inheritance tables from September to Decembe= r or appropriate.4. while creating=C2=A0inheritance tables, skip one of th= e tables which updated in the=C2=A0trigger function5. If you started to in= sert, it would write into the master table with a future date. TBH, I strongly doubt that anyone is going to follow up on this report as given. It seems at least as likely that the bug is in your trigger code as in Postgres proper. Without the exact schema and trigger code, anyone who did try couldn't be sure whether failure to see something interesting means that there's no Postgres bug or just that they'd failed to duplicate what you did. If you'd like us to take an interest, please submit a *self contained* test case. Preferably a script that starts with an empty database, creates all the requisite objects, and then does whatever is needed to exhibit the misbehavior. regards, tom lane