| From: | "Mike Sofen" <msofen(at)runbox(dot)com> |
|---|---|
| To: | "'pgsql-sql'" <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: Long running processes and commit writing to disk |
| Date: | 2022-04-08 16:52:23 |
| Message-ID: | 02f801d84b69$06336370$129a2a50$@runbox.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
From: Shaozhong SHI <shishaozhong(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2022-04-08 17:05:08 | Re: Long running processes and commit writing to disk |
| Previous Message | Shaozhong SHI | 2022-04-08 16:39:50 | Long running processes and commit writing to disk |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2022-04-08 17:05:08 | Re: Long running processes and commit writing to disk |
| Previous Message | Shaozhong SHI | 2022-04-08 16:39:50 | Long running processes and commit writing to disk |