| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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 20:42:18 |
| Message-ID: | 54C160AA.8070800@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/22/15 1:43 PM, Alvaro Herrera wrote:
> 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 ...
Yeah, I don't know that we actually want #2. It's bad enough to copy an entire database locally, but to then put it's entire contents into WAL? Blech.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2015-01-22 20:48:37 | Re: pg_upgrade and rsync |
| Previous Message | Jim Nasby | 2015-01-22 20:34:48 | Re: pg_upgrade and rsync |