Re: ON COMMIT options for non temporary tables

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: P V Tekawade <pvtekawade(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: ON COMMIT options for non temporary tables
Date: 2019-11-21 16:13:31
Message-ID: b944e45c61ebb397693958e6927c4c235885e1d2.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 2019-11-21 at 21:23 +0530, P V Tekawade wrote:
> For my work with Postgres 11.5, I needed functionality that unlogged tables
> are automatically dropped at the commit time, but I found that ON COMMIT
> option is only supported with temporary table.
> I would like to understand reasons why this option is limited to temporary tables?
> Is there any problem by making this option available for other type of tables
> such as unlogged tables?

How should that work for tables other than temporary tables?
Should COMMIT lock if somebody else accesses the table?

What keeps you from explicitly dropping the table right before
you commit?

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marc Millas 2019-11-21 16:14:38 Re: Extract transaction from WAL
Previous Message Adrian Klaver 2019-11-21 16:10:51 Re: Remote Connection Help