pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: George Wilk <gwilk@ellacoya.com>
To: pgsql-admin@postgresql.org
Subject: archive_command does not execute
Date: Tue, 19 Jun 2007 08:17:32 -0400
Message-ID: <002c01c7b26b$d0085400$0d7ba8c0@ellacoya.com> (raw)

Hi,

 

I am attempting to use the WAL archiving on a Solaris machine, running
PostgreSQL 8.1.4.  The archive_command specified in the postgresql.conf file
does not get executed, nor do I see any log entries showing errors etc.
What am I doing wrong here?  

 

Here is the relevant fragment of my conf file:

 

fsync = on                              # turns forced synchronization on or
off

wal_sync_method = fsync         # the default is the first option

                                        # supported by the operating system:

                                        #   open_datasync

                                        #   fdatasync

                                        #   fsync

                                        #   fsync_writethrough

                                        #   open_sync

#full_page_writes = on                  # recover from partial page writes

#wal_buffers = 8                        # min 4, 8KB each

#commit_delay = 0                       # range 0-100000, in microseconds

#commit_siblings = 5                    # range 1-1000

 

# - Checkpoints -

 

checkpoint_segments = 1         # in logfile segments, min 1, 16MB each

checkpoint_timeout = 30         #  range 30-3600, in second

checkpoint_warning = 5          # in seconds, 0 is off

 

# - Archiving -

 archive_command = 'touch /var/lib/pgsql/bkp/myfile'

 

 

Here is my log entry for the duration of the test:

 

FATAL:  terminating connection due to administrator command

LOG:  shutting down

LOG:  database system is shut down

LOG:  database system was shut down at 2007-06-19 07:48:03 EDT

LOG:  checkpoint record is at 0/899E68

LOG:  redo record is at 0/899E68; undo record is at 0/0; shutdown TRUE

LOG:  next transaction ID: 2445; next OID: 16399

LOG:  next MultiXactId: 1; next MultiXactOffset: 0

LOG:  database system is ready

LOG:  transaction ID wrap limit is 2147484146, limited by database
"postgres"

 

Thanks in advance,

 

~george

view thread (4+ messages)  latest in thread

Message-ID: <002c01c7b26b$d0085400$0d7ba8c0@ellacoya.com>
Permalink:  ../002c01c7b26b$d0085400$0d7ba8c0@ellacoya.com/
Also on:    postgresql.org/message-id/002c01c7b26b$d0085400$0d7ba8c0@ellacoya.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: gwilk@ellacoya.com
  Subject: Re: archive_command does not execute
  In-Reply-To: <002c01c7b26b$d0085400$0d7ba8c0@ellacoya.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