heads up -- subtle change of behavior of new initdb

I just noticed tonight that the new initdb introduced a subtle change of 
behavior. I use a shell script to automate the process of
- rm old data directory
- mkdir new data directory
- initdb
- load from pgdumpall
Now, that second step is not needed, but as of today it produces an 
installation that won't start due to improper permissions on data

Thought it was worth mentioning, or possibly reinstating old behavior.

Joe