H_H‭ Thanks for providing more information to clarify your situation! However your edit changed the premise of your question quite a bit and the answer you already got no longer fits your question.

Can you please roll-back your edit and instead ask a new follow-up question including the new information? Like this Canina‭'s answer here can be useful for future users who don't happen to want to move their DB and you're problem will hopefully get a suitable answer in your new question.

Sorry, i don't see how this makes the question different. In both cases i asked how to create a dump without having writes to the database that aren't in the dump.

The answer from Canina doesn't answer that, as she said at the beginning.

I'm not a SME for data bases, but without the constrain that you want to move your DB, you would not have to be concerned about a client writing to the database after dump is done, would you? So this additional constrain of yours seems to change the situation.

you would not have to be concerned about a client writing to the database after dump is done, would you?

As far as i see, that was mentioned in the question. Or isn't

so that no new writes to the database can be made

clear enough that the question is about a way to get a dump and preventing writes to the database?

That could even be the case in other situation where the database should not be moved. For example a situation where you don't want to change the database or only have a read only system.

This might or might not be the case, but your original question and the answer might nevertheless be useful for other users and a new question would give you the opportunity to clearly explain your situation without any cost or disadvantages for you.

Ok, thank you. made a new question https://powerusers.codidact.com/posts/290195

H_H‭ Thank you!