Tom Lane wrote:Ruslan A Dautkhanov <[EMAIL PROTECTED]> writes:I have experience with PostgreSQL 7.x, and I can't figure out why this happen. PG didn't say anything meaningful, that can point me why he did not start.That's fairly unusual --- I can't think of any places where the postmaster will exit without printing *some* complaint. # ./pg_controldata /usr/local/pgsql/data pg_control version number: 74 Catalog version number: 200411041 Database system identifier: 4786296063829923563 Database cluster state: in production pg_control last modified: среда, 22 июня 2005 г. 03:12:28 Current log file ID: 0 Next log file segment: 13 Latest checkpoint location: 0/C1DB058 Prior checkpoint location: 0/C0E47BC Latest checkpoint's REDO location: 0/C1DB058 Latest checkpoint's UNDO location: 0/0 Latest checkpoint's TimeLineID: 1 Latest checkpoint's NextXID: 133213 Latest checkpoint's NextOID: 492366 Time of latest checkpoint: среда, 22 июня 2005 г. 03:12:28 Database block size: 8192 Blocks per segment of large relation: 131072 Bytes per WAL segment: 16777216 Maximum length of identifiers: 64 Maximum number of function arguments: 32 Date/time type storage: floating-point numbers Maximum length of locale name: 128 LC_COLLATE: ru_RU.KOI8-R LC_CTYPE: ru_RU.KOI8-R Please note different values in "Latest checkpoint location" and "Prior checkpoint location" - is this mean that DB shutted down abnormally and some uncommited data exists? Maybe Postgres can't commit this changes? Btw, before this version I use PG 8.0.2 and after this I install 8.0.3, that can't startup... :/ Maybe 8.0.3 conflict with DB created in 8.0.2 ? Thanks a lot for your comments. -- Ruslan A Dautkhanov |
smime.p7s
Description: S/MIME Cryptographic Signature