Postgres Pro
Downloads
Home   >   mailing lists

RE: Long running processes and commit writing to disk - Mailing list pgsql-sql

From Mike Sofen
Subject RE: Long running processes and commit writing to disk
Date
Msg-id 02f801d84b69$06336370$129a2a50$@runbox.com
Whole thread Raw
In response to Long running processes and commit writing to disk  (Shaozhong SHI <shishaozhong@gmail.com>)
Responses Re: Long running processes and commit writing to disk  (Rob Sargent <robjsargent@gmail.com>)
List pgsql-sql
Tree view

From: Shaozhong SHI <shishaozhong@gmail.com>   Sent: Friday, April 08, 2022 9:39 AM

When long running processes got disrupted, one may not see any expected result.

How to make sure that the result of each operation is saved to disk in a loop?

Regards,

David

 

 

Simple:  don’t use a database – you’re asking to violate ACID. 

 

A database’s power comes from set-based operations.  You’re asking to do single row operations.  Use a spreadsheet...or a plain text file and treat it like a log.

 

Mike

pgsql-sql by date:

Previous
From: Shaozhong SHI
Date:
Subject: Long running processes and commit writing to disk
Next
From: Rob Sargent
Date:
Subject: Re: Long running processes and commit writing to disk