pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Davies <tgdavies@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: on-line backup questions
Date: Sat, 22 Dec 2007 16:20:26 +1100
Message-ID: <76654B35-D2A4-4167-81A0-F748E0263348@gmail.com> (raw)
In-Reply-To: <15488.1198290830@sss.pgh.pa.us>
References: <0FBA939C-2ED1-4400-BD3B-5290193837D0@gmail.com>
	<15488.1198290830@sss.pgh.pa.us>

Thanks for the prompt response!

On 22/12/2007, at 1:33 PM, Tom Lane wrote:

> Tom Davies <tgdavies@gmail.com> writes:
>>
>> 3. What's the best thing to do when I deliberately shut down
>> PostgreSQL (i.e. pg_ctl stop)? When I start again I will be restoring
>> from the most recent backup and rolling forward over the archived WAL
>> files. I believe that shutdown leaves me with unarchived WAL files in
>> pg_xlog.
>
> Yeah, you should archive the latest WAL file, but in 8.0 you'd have to
> do that manually.  (IIRC there isn't even a forced-xlog-switch  
> function
> in that version to help you.)

So in 8.2, when I do a backup I *don't* need to manually copy any WAL  
files?, and when I shut down I should:

1 call pg_switch_xlog()
2 wait for the WAL to be archived *if* pg_switch_xlog return a  
location after the end of the previously archived WAL
3 actually call pg_ctl stop

Do I need to do 2, above, or can postgres wait until the previous WAL  
archive is complete?

Thanks,
   Tom



view thread (3+ messages)

Message-ID: <76654B35-D2A4-4167-81A0-F748E0263348@gmail.com>
Permalink:  ../76654B35-D2A4-4167-81A0-F748E0263348@gmail.com/
Also on:    postgresql.org/message-id/76654B35-D2A4-4167-81A0-F748E0263348@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgdavies@gmail.com
  Subject: Re: on-line backup questions
  In-Reply-To: <76654B35-D2A4-4167-81A0-F748E0263348@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox