Skip site navigation (1) Skip section navigation (2)

Odd message with initdb on latest HEAD

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Odd message with initdb on latest HEAD
Date: 2005-06-29 04:01:40
Message-ID: 42C21D24.5000600@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-hackers
I run initdb and get:

LOG:  database system was shut down at 2005-06-29 11:57:10 WST
LOG:  checkpoint record is at 0/353E68
LOG:  redo record is at 0/353E68; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 548; next OID: 10792
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system is ready
LOG:  transaction ID wrap limit is 2147484132, limited by database 
"postgres"
LOG:  checkpoints are occurring too frequently (1 seconds apart)
HINT:  Consider increasing the configuration parameter 
"checkpoint_segments".
LOG:  transaction ID wrap limit is 2147484132, limited by database 
"postgres"

What's going on in initdb now that we are checkpointing too quickly?

Chris


Responses

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2005-06-29 04:06:26
Subject: Re: Feature request from irc...
Previous:From: Tom LaneDate: 2005-06-29 03:58:59
Subject: Re: [HACKERS] Avoiding io penalty when updating large objects

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group