01:51
*An:* pgsql-general@lists.postgresql.org
*Betreff:* [Extern] Re: consistent postgresql snapshot
On 5/11/22 10:41, Zwettler Markus (OIZ) wrote:
PostgreSQL12 running on CentOS7 + ext4.
Would it be save to do a "fsfreeze –freeze" + disk snapshot +
"fsfreeze –unf
Talking about fsfreeze and blocksize are not relevant in your case at all.
You can't make a backup this way any way. According your mail,
you are playing with database recovery after crash. Is pg crash proof? Yes (
https://www.postgresql.org/docs/current/wal-intro.html).
You can use this solution f
On Thu, 12 May 2022 at 14:48, Tom Lane wrote:
> "Zwettler Markus (OIZ)" writes:
> > I don't want to do use the normal backup algorithm where pg_start_backup
> + pg_stop_backup will fix any fractured block and I am required to have all
> archived logfiles, therefore.
> > I want to produce an atom
"Zwettler Markus (OIZ)" writes:
> I don't want to do use the normal backup algorithm where pg_start_backup +
> pg_stop_backup will fix any fractured block and I am required to have all
> archived logfiles, therefore.
> I want to produce an atomic consistent disk snapshot.
[ shrug... ] You can'
n] Re: consistent postgresql snapshot
On 5/11/22 10:41, Zwettler Markus (OIZ) wrote:
PostgreSQL12 running on CentOS7 + ext4.
Would it be save to do a "fsfreeze –freeze" + disk snapshot + "fsfreeze
–unfreeze" of the PGDATA filesystem to get a consistent snapshot?
I am wonder
On 5/11/22 10:41, Zwettler Markus (OIZ) wrote:
PostgreSQL12 running on CentOS7 + ext4.
Would it be save to do a "fsfreeze –freeze" + disk snapshot + "fsfreeze
–unfreeze" of the PGDATA filesystem to get a consistent snapshot?
I am wondering as PostgreSQL default blocksize = 8k while ext4 defa
PostgreSQL12 running on CentOS7 + ext4.
Would it be save to do a "fsfreeze -freeze" + disk snapshot + "fsfreeze
-unfreeze" of the PGDATA filesystem to get a consistent snapshot?
I am wondering as PostgreSQL default blocksize = 8k while ext4 default
blocksize = 4k, resulting in 2 fs blocks per d
