From: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
---|---|
To: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Adding PRIMARY KEY info |
Date: | 1998-09-03 14:46:55 |
Message-ID: | m0zEaf1-00006FC@druid.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thus spake Bruce Momjian
> > I tried adding the PRIMARY KEY info to pg_class but the resulting data
> > base system simply dumps core everywhere. Can someone point me to the
>
> My recommendation is to find a seldom-used field in pg_class, like
> relchecks, and find all instances of that in the code, and add code for
> your new field in all those places. You need to assign the value in
> call cases where you are inserting into pg_class, not just the initdb
> stuff.
Does this relate to the core dumping? Since there is so far no code
using this field, how would adding a field dump core? Can you see
anything in my description of what I did to account for this.
Your suggestion sounds good for the next step though. Thanks.
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
From | Date | Subject | |
---|---|---|---|
Next Message | D'Arcy J.M. Cain | 1998-09-03 14:56:43 | Re: [HACKERS] Adding PRIMARY KEY info |
Previous Message | David Hartwig | 1998-09-03 14:41:29 | Re: [HACKERS] index fix report |