RE: Complete data erasure

Hello, I was off the point. I want to organize the discussion and suggest feature design. There are two opinions. 1. COMMIT should not take a long time because errors are more likely to occur. 2. The data area should be released when COMMIT is completed because COMMIT has to be an atomic action.

RE: Conflict handling for COPY FROM

Hello Surafel, From: Surafel Temesgen >An error that can be surly handled without transaction rollback can >be included in error handling but i will like to proceed without binary file >errors handling for the time being Thank you. Also it seems that you apply Alexey's comment. So I'll mark thi

RE: ssl passphrase callback

Hello Andrew, From: Andreas Karlsson > # Nitpicking > > The certificate expires in 2030 while all other certificates used in > tests expires in 2046. Should we be consistent? > > There is text in server.crt and server.key, while other certificates and > keys used in the tests do not have this.

RE: Complete data erasure

Hello Tom, From: asaba.takan...@fujitsu.com > Hello Tom, > > From: Tom Lane > > Tomas Vondra writes: > > > I think it depends how exactly it's implemented. As Tom pointed out in > > > his message [1], we can't do the erasure itself in the post-comm

RE: Conflict handling for COPY FROM

Hello Surafel, From: Surafel Temesgen >>On Fri, Mar 6, 2020 at 11:30 AM mailto:asaba.takan...@fujitsu.com >> wrote: >>I think we need regression test that constraint violating row is returned >>back to the caller. >>How about this? > >okay attached is a rebas

RE: Conflict handling for COPY FROM

Hello Surafel, Sorry for my late reply. From: Surafel Temesgen >On Thu, Dec 12, 2019 at 7:51 AM mailto:asaba.takan...@fujitsu.com > wrote: >>2. I have a question about copy meta-command. >>When I executed copy meta-command, output wasn't displayed. >>Does it

RE: Complete data erasure

Hello Tom, From: Tom Lane > Tomas Vondra writes: > > I think it depends how exactly it's implemented. As Tom pointed out in > > his message [1], we can't do the erasure itself in the post-commit is > > not being able to handle errors. But if the files are renamed durably, > > and the erasure hap

RE: Complete data erasure

Greetings, From: asaba.takan...@fujitsu.com > Hello Stephen, > > From: Stephen Frost > > I disagree- it's a feature that's been asked for multiple times and does > > have value in some situations. > > I'm rethinking the need for this feature althou

RE: Complete data erasure

Hello Stephen, From: Stephen Frost > I disagree- it's a feature that's been asked for multiple times and does > have value in some situations. I'm rethinking the need for this feature although I think that it improves the security. You said that this feature has value in some situations. Could

RE: Complete data erasure

Hello Stephen, Thank you for comment. From: Stephen Frost > Greetings, > > * asaba.takan...@fujitsu.com (asaba.takan...@fujitsu.com) wrote: > > This feature erases data area just before it is returned to the OS (“erase” > means that overwrite data area to hide its contents

RE: Complete data erasure

Hello, Horiguchi-san Thank you for comment. At Wed, 15 Jan 2020 03:46 +, "Kyotaro Horiguchi " wrote in > shred(1) or wipe(1) doesn't seem to contribute to the objective on > journaled or copy-on-write file systems. I'm not sure, but maybe the > same can be true for read-modify-write devices

Complete data erasure

Hello hackers, I want to add the feature to erase data so that it cannot be restored because it prevents attackers from stealing data from released data area. - Background International security policies require that above threat is taken measures. It is "Base Protection Profile for Database Man

RE: Conflict handling for COPY FROM

Hello Surafel, I'm very interested in this patch. Although I'm a beginner,I would like to participate in the development of PostgreSQL. 1. I want to suggest new output format. In my opinion, it's kind to display description of output and add "line number" and "error" to output. For example, e