Re: skipping pg_log in basebackup (was Re: pg_basebackup and pg_stat_tmp directory)

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Mitsumasa KONDO <kondo(dot)mitsumasa(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tomáš Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: skipping pg_log in basebackup (was Re: pg_basebackup and pg_stat_tmp directory)
Date: 2015-06-10 17:12:58
Message-ID: 5578701A.7070507@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 06/10/2015 10:01 AM, Andres Freund wrote:
>
> On 2015-06-10 09:57:17 -0700, Jeff Janes wrote:
>> Mine goal isn't that. My goal is to have a consistent backup without
>> having to shut down the server to take a cold one, or having to manually
>> juggle the pg_start_backup, etc. commands.
>
> A basebackup won't necessarily give you a consistent log though...

I am -1 on this idea. It just doesn't seem to make sense. There are too
many variables where it won't work or won't be relevant.

JD

--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-06-10 17:19:14 Re: s_lock() seems too aggressive for machines with many sockets
Previous Message Robbie Harwood 2015-06-10 17:02:53 Re: Postgres GSSAPI Encryption