Odd message with initdb on latest HEAD

Started by Christopher Kings-Lynneover 20 years ago2 messages
#1Christopher Kings-Lynne
chriskl@familyhealth.com.au

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

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Christopher Kings-Lynne (#1)
Re: Odd message with initdb on latest HEAD

Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:

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

Hm, haven't seen that myself, but I bet it's because (a) create database
now forces checkpoint, and (b) we now do two of 'em in a row.

This seems worth fixing, but it is just cosmetic, so I don't plan to
panic about it this week ...

regards, tom lane