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 TYAPR01MB2990C8CD6F13D48DF226FC3FFE640@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Implement UNLOGGED clause for COPY FROM  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers

From: David G. Johnston <david.g.johnston@gmail.com>

> This step seems to invalidate the idea outright.  The checkpoint command is superuser only and isn’t table specific.  This seems to require both those things to be changed.

 

Perhaps FlushRelationBuffers() followed by smgrsync() can be used instead.  Or, depending on the assumed use case (e.g. the DBA adds data regularly for analytics), we may allow COPY UNLOGGED to be used only by superusers and some special pg_ roles, and COPY UNLOGGED performs checkpoints.  Anyway, I kind of feel that COPY UNLOGGED needs some special privileges, because it renders the table unrecoverable and not being replicated to the standby.

 

 

Regards

Takayuki Tsunakawa

 

pgsql-hackers by date:

Previous
From: "movead.li@highgo.ca"
Date:
Subject: Re: A patch for get origin from commit_ts.
Next
From: Amit Khandekar
Date:
Subject: Re: calling procedures is slow and consumes extra much memory against calling function