RE: Implement UNLOGGED clause for COPY FROM - Mailing list pgsql-hackers

From tsunakawa.takay@fujitsu.com
Subject RE: Implement UNLOGGED clause for COPY FROM
Date
Msg-id TYAPR01MB299011CD2A25066D5CC161F6FE270@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Implement UNLOGGED clause for COPY FROM  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: Implement UNLOGGED clause for COPY FROM
List pgsql-hackers
From: Peter Smith <smithpb2250@gmail.com>
> Earlier, Osumi-san was rejecting the idea of using ALTER TABLE tbl SET
> UNLOGGED on basis that it is too time consuming for large data to
> switch the table modes [1].

> Doesn't wal_level=none essentially just behave as if every table was
> UNLOGGED; not just the ones we are loading?
> 
> Doesn't wal_level=none come with all the same limitations/requirements
> (full daily backups/restarts etc) that the UNLOGGED TABLE would also
> have?

ALTER TABLE takes long time proportional to the amount of existing data, while wal_level = none doesn't.


Regards
Takayuki Tsunakawa


pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Minor cleanup of partbounds.c
Next
From: Amit Kapila
Date:
Subject: Re: Bug in logical decoding of in-progress transactions