| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Gokan Atmaca <linux(dot)gokan(at)gmail(dot)com> |
| Cc: | Victor Yegorov <vyegorov(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PgBackRest PITR restore |
| Date: | 2021-09-13 19:43:55 |
| Message-ID: | 20210913194355.GG17906@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Greetings,
* Gokan Atmaca (linux(dot)gokan(at)gmail(dot)com) wrote:
> > Look for --db-include
>
> This option restores a single database but corrupts the others. Is it
> necessary to take a backup with "pg_dump" before doing this?
"Corrupts" is only kind of correct- it explicitly doesn't restore the
other databases (since you asked for just one to be restored) and makes
it such that you're not able to log into them.
Performing an export with pg_dump is one approach to getting a point in
time view of all of the data in a given database, but you won't be able
to perform PITR-style restore with pg_dump's.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-09-13 20:20:00 | Re: Estimating HugePages Requirements? |
| Previous Message | Bossart, Nathan | 2021-09-13 18:49:16 | Re: Estimating HugePages Requirements? |