Re: [HACKERS] Problem in S_LOCK?

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk>
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Problem in S_LOCK?
Date: 1999-05-24 21:07:04
Message-ID: 199905242107.RAA26278@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I just tried initdb and:

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
#$ aspg postgres -D /u/pg/data 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>

and it worked.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-05-24 21:20:32 Re: [HACKERS] Open 6.5 items
Previous Message Ari Halberstadt 1999-05-24 18:45:24 pg_dump core dumps