Re: basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe?

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe?
Date: 2015-01-22 19:43:45
Message-ID: 20150122194345.GF1663@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund wrote:

> 2) Make movedb() (and possibly created(), not sure yet) use proper WAL
> logging and log the whole copied data. I think this is the right long
> term fix and would end up being much more reliable. But it either
> requires some uglyness during redo (creating nonexistant database
> directories on the fly during redo) or new wal records.
>
> Doable, but probably too large/invasive to backpatch.

Not to mention the extra WAL traffic ...

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2015-01-22 20:01:03 Re: proposal: plpgsql - Assert statement
Previous Message Jim Nasby 2015-01-22 19:36:04 Re: Proposal: knowing detail of config files via SQL