PostgreSQL Backup & Point-In-Time Recovery

PostgreSQL Backup & Point-In-Time Recovery

Scaling Postgres

6 лет назад

64,162 Просмотров

Ссылки и html тэги не поддерживаются


Комментарии:

f5edy
f5edy - 13.07.2023 18:41

man you helped me a lot

Ответить
Meu canal
Meu canal - 05.07.2023 22:53

Do managed databases in aws and gcp have this built-in ?

Ответить
Chirag Karkera
Chirag Karkera - 15.02.2023 12:55

Best explanation. Thank You

Ответить
Shah Alam
Shah Alam - 01.01.2023 14:24

Thank you very much for a detail and informative tutorial

Ответить
amardeep kumar
amardeep kumar - 26.12.2022 20:01

Great explanation .thank you

Ответить
tanish krishna datta
tanish krishna datta - 30.06.2022 10:51

Hi ,
default archive log file size is 16mb and can we reduce the size of archive log file.(i use the compressed version and it will reduce 16mb to 20k).but with out compression i need other solution .can u advise in this ?

Ответить
Anderson Stachera
Anderson Stachera - 20.05.2022 18:32

Hello. In the archive_command parameter where you put 'test ! -f /home/...' this 'test' is the name of the data base I have or leave it as you added it to the command line with the test itself?

Ответить
Gustavo Gomez
Gustavo Gomez - 19.04.2022 05:04

Great video!! Thanks!!!!

Ответить
ranvijay mehta
ranvijay mehta - 24.03.2022 22:34

Thank you so much

Ответить
skizzi
skizzi - 29.12.2021 12:51

Is it really necessary to use the restore_command if not doing a point in time recovery? The basebackup generates a full valid backup and so it should not be necessary to use the restore_command to use wal files from the archive folder, right?

Ответить
Maly Mohsem
Maly Mohsem - 09.12.2021 11:10

Hey, I Have been stuck after the "pg_basebackup -Ft -X none -D - | gzip > /var/lib/postgresql/db_file_backup.tar.gz" command line. it shows "pg_stop_backup still waiting for all required WAL segments to be archived (3840 seconds elapsed)" which means it has already taken 1 hour and continuing. Is it normal or just happening to me?

Ответить
Leon
Leon - 26.08.2021 22:14

Can you please make a video to do postgres 13 incremental backup and replication in windows version

Ответить
Md. Imrul Hasan
Md. Imrul Hasan - 26.07.2021 18:46

After running the command in my pg-13
sudo service postgresql restart
It could not restart

After the command when I use ~$ psql

It shows

"error: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?"

Ответить
Draz
Draz - 22.07.2021 19:32

If you do a PITR, doesn't all the data inserted after the restore point still get saved to the WAL files?
So after the restore procedure, those WAL files still exist, right? Wouldn't that cause issues for future restores?
You essentially wanted to get rid of that data, but if you were to do a new restore without specifying a restore point, the data would return.

Ответить
bhanu konthala
bhanu konthala - 14.07.2021 10:01

because you just edited the recovery.conf

Ответить
bhanu konthala
bhanu konthala - 14.07.2021 09:59

Thanks for the tutorial and i want know how we can add the recovery.conf to particular directory?

Ответить
Caleb Mbugua
Caleb Mbugua - 01.04.2021 05:59

Thanks so much...i really have enjoye this

Ответить
Rodrigo Mendoza
Rodrigo Mendoza - 24.01.2021 22:11

hello, one question, is it possible to recover the database after applying a drop to the entire database?

Ответить
Balvanth Reddy
Balvanth Reddy - 12.01.2021 07:10

Hi , Im new to PostgreSQL.. but it's very easy to understanding concepts. thanks for your video.

Ответить
Vikram Godara
Vikram Godara - 10.01.2021 15:33

Hi, Thanks for sharing the wonderful information it's helping me to compare the operation in Postgres as I am oracle dba.

Ответить