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 1l43hq-0006eQ-TN for pgsql-docs@arkaria.postgresql.org; Mon, 25 Jan 2021 15:23:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l43hp-0004th-Ns for pgsql-docs@arkaria.postgresql.org; Mon, 25 Jan 2021 15:23:05 +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 1l43hp-0004ta-E0 for pgsql-docs@lists.postgresql.org; Mon, 25 Jan 2021 15:23:05 +0000 Received: from mail-ej1-x632.google.com ([2a00:1450:4864:20::632]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l43hm-0003iI-AL for pgsql-docs@lists.postgresql.org; Mon, 25 Jan 2021 15:23:04 +0000 Received: by mail-ej1-x632.google.com with SMTP id r12so18527860ejb.9 for ; Mon, 25 Jan 2021 07:23:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=KiDAqGZ5w4bOEHjxkPN9qlrs/03CDa+IqI22ndA2hKI=; b=S3kN1/+zZ3+rFTJc8Bx/4/mkzutZVi3Db92uIBdX3LyKQu6AtLZ/r2IziInJdW8tMw DZzBml9+aWtKvEw6pN5017FluVwHiFmHiunf4Y3NYapQSHzPceXOgtBFs2QlOs7Ekp/z dsU960k6AL3XIc9nEzhBIo554m2i+61incRlOyLyIKP2PplEfyRzArVTY44F5/J/Y9a0 XLne9QbLEnYbMIxa7eQQ65H+5YRVpNn9TA+mzQGD/pJ44hvk5xKx1GBKDYwZYdyqnf+F X7sKD8dTgvr8SQNvQfVPvdfs2Ij2vyLH2Y3/Nx8vMHIXhbT/caumjd0DAZkas+sCZB1U sC1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=KiDAqGZ5w4bOEHjxkPN9qlrs/03CDa+IqI22ndA2hKI=; b=JhceM2nRDgc7n/r9CG5K4nMWaa2kHW/feuVFDLKAE2WbIwDjI6Bxpqkxcz1g3TLJLU a756BfHioEHUglzTzsKaWUqrwWcz5/gXzhNfhiHWDGEtU2d/qWUJv4fXncie/RdzRRKE tbjGd15RSEXioRTXVCTJLetMnn0ND4hGFp15nRcaFWrOLgCNHqnuCO995oa/aBv5dNMg u14YTQ86+vipDez7I6GjsuUrkRN3FiDBKIde1nMGtgJIqv6c+mvicOdtZMjmp2aQqa2W M1cZgIS5oP3qpOWlU9QrU9zoLF0iR51NnntM4qfd6yjFqJk6HXbhbbrJp6mXdMGHQMnN FJXg== X-Gm-Message-State: AOAM532DbyXoyXFew2FBxoLuG4s31+R+eQfiM0KySzZ2iVNgr79THI4g 96W347lT+0IhhePRJV0OHiJcEw== X-Google-Smtp-Source: ABdhPJxmMoXWvCVmItF1D0CLGmiN6KFPfndkjlxyrzenEQgwdGTDxuuy8O/nHfqq2nbb86JkH2zDBQ== X-Received: by 2002:a17:906:7cd8:: with SMTP id h24mr657835ejp.511.1611588180171; Mon, 25 Jan 2021 07:23:00 -0800 (PST) Received: from localhost.localdomain (62-47-149-60.adsl.highway.telekom.at. [62.47.149.60]) by smtp.gmail.com with ESMTPSA id k22sm10932603edv.33.2021.01.25.07.22.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 25 Jan 2021 07:22:59 -0800 (PST) Message-ID: <56514982026dea49ebb6ee33fab28e13daa9b6f5.camel@cybertec.at> Subject: Re: TRUNCATE VIEW From: Laurenz Albe To: harisai hari Cc: pgsql-docs@lists.postgresql.org Date: Mon, 25 Jan 2021 16:22:58 +0100 In-Reply-To: References: <161157636877.14625.15340884663716426087@wrigleys.postgresql.org> <4d8ee45bb0d07a09da5d64d6cba114e7db5777b3.camel@cybertec.at> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, 2021-01-25 at 18:45 +0530, harisai hari wrote: > > On Mon, 25 Jan 2021, 6:08 pm Laurenz Albe, wrote: > > On Mon, 2021-01-25 at 12:06 +0000, PG Doc comments form wrote: > > > In this link https://www.postgresql.org/docs/12/ddl-priv.html you mentioned > > > like Truncate of view, Is it possible? > > > > > > TRUNCATE > > > Allows TRUNCATE on a table, view, etc. > > > > Yes, if you define an INSTEAD OF TRUNCATE trigger on the view. > > Could you please provide documentation link, I couldn't find it. Checking again, I realize that I wrote nonsense, and you are right. I concur that this should be simplified to Allows TRUNCATE on a table. Yours, Laurenz Albe