| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | 厚积薄发 <postgresql_2016(at)163(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: GIN index vacuum hang after pg_rman restore in PG9.2.21 |
| Date: | 2017-06-16 00:32:41 |
| Message-ID: | ca14cb09-2ad9-7838-3c5e-ebbccc615ac4@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2017/06/16 8:48, 厚积薄发 wrote:
> I also test it with postgresql9.6.3 and pg_rman
> 1.3.4(https://github.com/ossc-db/pg_rman/releases/download/v1.3.4/pg_rman-1.3.4-pg96.tar.gz).
> However, it has the same problem.
>
> In my view, pg-rman just do PITR which contains pg_start_backup,copy files
> and pg_stop_backup steps,it will not affect the tuple page theoretically.
Actually, pg_rman does manipulate data pages to store backup data in its
own specific format, so it might as well be a problem of pg_rman too,
which I suspect it is.
It would be better to contact the pg_rman community about this:
https://github.com/ossc-db/pg_rman/issues
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-06-16 01:32:22 | Re: BUG #14708: Frequent connection timeout issue while connecting to Postgres database |
| Previous Message | 厚积薄发 | 2017-06-15 23:48:24 | Re: GIN index vacuum hang after pg_rman restore in PG9.2.21 |