Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] duplicate oids in pg_proc

From: t-ishii(at)sra(dot)co(dot)jp
To: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: t-ishii(at)sra(dot)co(dot)jp, hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] duplicate oids in pg_proc
Date: 1998-06-02 00:52:18
Message-ID: 199806020052.JAA01540@srapc451.sra.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
>> > There are some duplicate oids in pg_proc of May30 snapshot.
>> > I know octet_length's are from my patch but for others I don't know.
>> > Comments?
>> 
>> Those must be mine (char, char_bpchar, bpchar, bpchar_char). I am sure
>> that I ran ./unused_oids to assign them, but obviously messed it up.
>> Will reassign soon. Darn :(
>
>Oh, I see what happened. I developed on a revlocked tree from 980513 and
>then patched the current tree and ran the regression tests. Patches
>applied cleanly and the regression tests passed, so I submitted the
>patches.
>
>In the meantime your patches used the same OIDs, and the regression test
>is apparently not sensitive to the overlap.
>
>Just to avoid confusion: only one of us should try to fix the problem :)
>Shall I, or are you already working on it?

Not yet. Could you solve the duplication? Thanks in advance,
--
Tatuso Ishii
t-ishii(at)sra(dot)co(dot)jp

pgsql-hackers by date

Next:From: The Hermit HackerDate: 1998-06-02 01:26:49
Subject: AbortTransaction and not in in-progress state
Previous:From: Stupor GeniusDate: 1998-06-02 00:44:23
Subject: RE: [HACKERS] Lots 'o patches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group