public inbox for [email protected]
help / color / mirror / Atom feedLong running processes and commit writing to disk
5+ messages / 4 participants
[nested] [flat]
* Long running processes and commit writing to disk
@ 2022-04-08 16:39 Shaozhong SHI <[email protected]>
2022-04-08 16:39 ` Long running processes and commit writing to disk Shaozhong SHI <[email protected]>
2022-04-08 16:52 ` RE: Long running processes and commit writing to disk Mike Sofen <[email protected]>
0 siblings, 2 replies; 5+ messages in thread
From: Shaozhong SHI @ 2022-04-08 16:39 UTC (permalink / raw)
To: pgsql-sql <[email protected]>
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Long running processes and commit writing to disk
2022-04-08 16:39 Long running processes and commit writing to disk Shaozhong SHI <[email protected]>
@ 2022-04-08 16:39 ` Shaozhong SHI <[email protected]>
2022-04-08 18:01 ` Re: Long running processes and commit writing to disk Ron <[email protected]>
1 sibling, 1 reply; 5+ messages in thread
From: Shaozhong SHI @ 2022-04-08 16:39 UTC (permalink / raw)
To: pgsql-general <[email protected]>
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Long running processes and commit writing to disk
2022-04-08 16:39 Long running processes and commit writing to disk Shaozhong SHI <[email protected]>
2022-04-08 16:39 ` Long running processes and commit writing to disk Shaozhong SHI <[email protected]>
@ 2022-04-08 18:01 ` Ron <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Ron @ 2022-04-08 18:01 UTC (permalink / raw)
To: [email protected]
On 4/8/22 11:39, Shaozhong SHI wrote:
>
> 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?
That would of course depend on how often you begin and commit transactions.
--
Angular momentum makes the world go 'round.
^ permalink raw reply [nested|flat] 5+ messages in thread
* RE: Long running processes and commit writing to disk
2022-04-08 16:39 Long running processes and commit writing to disk Shaozhong SHI <[email protected]>
@ 2022-04-08 16:52 ` Mike Sofen <[email protected]>
2022-04-08 17:05 ` Re: Long running processes and commit writing to disk Rob Sargent <[email protected]>
1 sibling, 1 reply; 5+ messages in thread
From: Mike Sofen @ 2022-04-08 16:52 UTC (permalink / raw)
To: 'pgsql-sql' <[email protected]>
From: Shaozhong SHI <[email protected]> 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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Long running processes and commit writing to disk
2022-04-08 16:39 Long running processes and commit writing to disk Shaozhong SHI <[email protected]>
2022-04-08 16:52 ` RE: Long running processes and commit writing to disk Mike Sofen <[email protected]>
@ 2022-04-08 17:05 ` Rob Sargent <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Rob Sargent @ 2022-04-08 17:05 UTC (permalink / raw)
To: [email protected]
On 4/8/22 10:52, Mike Sofen wrote:
>
> *From:* Shaozhong SHI <[email protected]> *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
>
Or commit every loop (perhaps every N loops, depending on how much
you're prepared to re-do.)
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2022-04-08 18:01 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-04-08 16:39 Long running processes and commit writing to disk Shaozhong SHI <[email protected]>
2022-04-08 16:39 ` Shaozhong SHI <[email protected]>
2022-04-08 18:01 ` Ron <[email protected]>
2022-04-08 16:52 ` Mike Sofen <[email protected]>
2022-04-08 17:05 ` Rob Sargent <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox