Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 9571E9FB986 for ; Tue, 19 Jun 2007 09:45:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 68927-05 for ; Tue, 19 Jun 2007 09:45:41 -0300 (ADT) X-Greylist: delayed 00:27:59.589236 by SQLgrey-1.7.5 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 9CAF69FBDB4 for ; Tue, 19 Jun 2007 09:45:38 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from mail02.ellacoya.com (67-135-29-172.dia.static.qwest.net [67.135.29.172]) by svr4.postgresql.org (Postfix) with ESMTP id C38B55AF87E for ; Tue, 19 Jun 2007 12:17:37 +0000 (GMT) Received: from YZANGXP ([192.168.123.13]) by mail02.ellacoya.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Jun 2007 08:17:34 -0400 From: "George Wilk" To: Subject: archive_command does not execute Date: Tue, 19 Jun 2007 08:17:32 -0400 Message-ID: <002c01c7b26b$d0085400$0d7ba8c0@ellacoya.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002D_01C7B24A.48F6B400" X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aceya8/kWZp/Oj5pTgaWtlUFRiDx3g== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-OriginalArrivalTime: 19 Jun 2007 12:17:34.0947 (UTC) FILETIME=[D180C330:01C7B26B] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-3.800.1026-15246.003 X-TM-AS-Result: No--15.228500-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.137 tagged_above=0 required=5 tests=BAYES_50=0.001, FORGED_RCVD_HELO=0.135, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200706/176 X-Sequence-Number: 25844 This is a multi-part message in MIME format. ------=_NextPart_000_002D_01C7B24A.48F6B400 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 ------=_NextPart_000_002D_01C7B24A.48F6B400 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 =3D on            = ;            =       # turns forced synchronization on or off

wal_sync_method =3D fsync         # the default is = the first option

         =             &= nbsp;           &n= bsp;      # supported by the operating system:

         =             &= nbsp;           &n= bsp;      #   open_datasync

         =             &= nbsp;           &n= bsp;      #   fdatasync

         =             &= nbsp;           &n= bsp;      #   fsync

         =             &= nbsp;           &n= bsp;      #   fsync_writethrough

         =             &= nbsp;           &n= bsp;      #   open_sync

#full_page_writes =3D on            = ;      # recover from partial page writes

#wal_buffers =3D = 8            =             # min 4, 8KB each

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

#commit_siblings =3D 5            =         # range 1-1000

 

# - Checkpoints -

 

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

checkpoint_timeout =3D 30         #  range = 30-3600, in second

checkpoint_warning =3D 5          # in seconds, 0 = is off

 

# - Archiving -

 archive_command =3D '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

------=_NextPart_000_002D_01C7B24A.48F6B400--