odd output in initdb
От | Andrew Dunstan |
---|---|
Тема | odd output in initdb |
Дата | |
Msg-id | 4B633E49.2010308@dunslane.net обсуждение исходный текст |
Ответы |
Re: odd output in initdb
|
Список | pgsql-hackers |
I saw some odd pgstat output during an initdb on Windows today: The files belonging to this database system will be owned by user "pgrunner". This user must also own the server process. The database cluster will be initialized with locale C. The default database encoding has accordingly been set to SQL_ASCII. The default text search configuration will be set to "english". creating directory data ... ok creating subdirectories ... ok selecting default max_connections ... 100 selectingdefault shared_buffers ... 32MB creating configuration files ... ok creating template1 database in data/base/1... ok initializing pg_authid ... ok initializing dependencies ... WARNING: pgstat wait timeout WARNING: pgstat wait timeout ok creating system views ... ok loading system objects' descriptions ... ok creatingconversions ... ok creating dictionaries ... ok setting privileges on built-in objects ... ok creating informationschema ... ok loading PL/pgSQL server-side language ... ok vacuuming database template1 ... WARNING: pgstatwait timeout WARNING: pgstat wait timeout ok copying template1 to template0 ... WARNING: pgstat wait timeout ok copying template1 to postgres ... ok Success. You can now start the database server using: "C:\msys\1.0\home\pgrunner\bf\root\HEAD\inst\bin\postgres" -D "data" or "C:\msys\1.0\home\pgrunner\bf\root\HEAD\inst\bin\pg_ctl"-D "data" -l logfile start WARNING: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the-A option the next time you run initdb. A little searching on the buildfarm shows this started around Jan 10th: pgbfprod=# select min(snapshot) from build_status_log where sysname = 'red_bat' and log_stage = 'initdb.log' and log_text~ 'pgstat'; min --------------------- 2010-01-10 23:30:01 (1 row) I can't see an obvious culprit in the commit logs right off. Does anyone have an idea what's going on? cheers andrew
В списке pgsql-hackers по дате отправления: