| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | 两个孩子的爹 <1726002692(at)qq(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 回复： BUG #15949: pg_basebackup failed(PG-12-Beta3) |
| Date: | 2019-08-13 02:36:11 |
| Message-ID: | 20190813023611.GC2551@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Aug 13, 2019 at 09:18:36AM +0800, 两个孩子的爹 wrote:
> I only tested PG-12-Beta 3.
> Backup completed normally, but did not seem to end correctly。
> Backup files are generated during the backup process, but nothing is
> left at the end of the backup process.
I have done a couple of tests with a couple of configurations:
- Instance with multiple tablespaces.
- wal_receiver_timeout and wal_sender_timeout set at 0
- Compression enabled with pg_basebackup, same as you at level 5
(worked even at higher levels).
- Tar format used.
Unfortunately I have no traces of failures in my own tests, and the
format of each tablespace tarballs was correct.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Piotr Włodarczyk | 2019-08-13 10:51:37 | Re: Recovery mode with partitioned tables and ANY(NULL) in WHERE clause |
| Previous Message | Thomas Munro | 2019-08-13 01:49:26 | Re: BUG #15952: UNIQUE CONSTRAINT does not fulfill its' purpose |