Re: BUG #13645: pg_basebackup backup hash index & unlogged table

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: digoal(at)126(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13645: pg_basebackup backup hash index & unlogged table
Date: 2015-10-05 01:37:41
Message-ID: 20151005013741.GA6797@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Sep 28, 2015 at 06:15:24AM +0000, digoal(at)126(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13645
> Logged by: digoal
> Email address: digoal(at)126(dot)com
> PostgreSQL version: 9.4.4
> Operating system: CentOS 6.x x64
> Description:
>
> HI,
> Hash index and unlogged table don't generate XLOG record, when we use
> pg_basebackup's backup datafile & xlog archive recovery database, unlogged
> table datafile will purged, and hash index also has unconsistent data page.
> Why pg_basebackup not filter the hash index datafile & unlogged table
> datafile, these file waste net band and backup file's capcity.

We will issue a warning in 9.5 when hash indexes are created. I am not
sure why we don't filter out hash indexed and unlogged tables.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2015-10-05 03:00:37 Re: BUG #13645: pg_basebackup backup hash index & unlogged table
Previous Message Jeff Janes 2015-10-03 19:26:50 Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica.