← Back to context Comment by Matl 21 hours ago Because it's a single file you can back up like any other? 2 comments Matl Reply rowanG077 21 hours ago I interpreted it as the problem being that the technology may end up unsupported. I mean you can also keep using pgbackrest now. It's not like the code is gone. Matl 20 hours ago Well, yes, I meant that you don't need any 'special' tooling for Sqlite, whereas you do for pg.
rowanG077 21 hours ago I interpreted it as the problem being that the technology may end up unsupported. I mean you can also keep using pgbackrest now. It's not like the code is gone. Matl 20 hours ago Well, yes, I meant that you don't need any 'special' tooling for Sqlite, whereas you do for pg.
Matl 20 hours ago Well, yes, I meant that you don't need any 'special' tooling for Sqlite, whereas you do for pg.
I interpreted it as the problem being that the technology may end up unsupported. I mean you can also keep using pgbackrest now. It's not like the code is gone.
Well, yes, I meant that you don't need any 'special' tooling for Sqlite, whereas you do for pg.