Re: [HACKERS] Problem in S_LOCK?
От | Thomas A. Szybist |
---|---|
Тема | Re: [HACKERS] Problem in S_LOCK? |
Дата | |
Msg-id | 199905270049.UAA10816@carmina.boxhill обсуждение исходный текст |
Ответ на | Re: [HACKERS] Problem in S_LOCK? (Keith Parks <emkxp01@mtcc.demon.co.uk>) |
Список | pgsql-hackers |
Well, good news and bad news. It seems to work for me. Sorry. This is a sparc10 running 2.0.30. Yes, very old. Soon I can give Red hat 6.0 a try on an Ultra10. [szybist@anka post]$ initdb We are initializing the database system with username szybist (uid=501). This user will own all the files and must also own the server process. Creating Postgres database system directory /home/szybist/post/data/base Creating template database in /home/szybist/post/data/base/template1 Creating global classes in /home/szybist/post/data/base Adding template1 database to pg_database... Vacuuming template1 Creating public pg_user view Creating view pg_rules Creating view pg_views Creating view pg_tables Creating view pg_indexes Loading pg_description [szybist@anka post]$ postgres template1 POSTGRES backend interactive interface $Revision: 1.115 $ $Date: 1999/05/22 17:47:49 $ backend> create database bench blank 1: datname (typeid = 19, len = 32, typmod = -1, byval = f) 2: datdba (typeid = 23, len = 4,typmod = -1, byval = t) 3: encoding (typeid = 23, len = 4, typmod = -1, byval = t) 4: datpath (typeid= 25, len = -1, typmod = -1, byval = f) ---- backend>
В списке pgsql-hackers по дате отправления: