From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Another bug in pg_operator.h |
Date: | 1998-10-29 18:02:43 |
Message-ID: | 199810291802.NAA20294@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Yes. See include/catalog/template1_check.sql. Uses SQL to do checks.
>
> Hmm. OK, that script has some overlap with what I did last night.
> But is it run automatically? I think putting the checks into a
> regression test is a better plan.
You were right, template1_check.sql is generated by
pgsql/contrib/findoidjoins/make_oidjoin_check.
It is not run automatically, but should be, just as duplicate_oids
should be.
>
> Also, in playing around with template1_check.sql, I discovered that
> pg_operator OID 644
>
> DATA(insert OID = 644 ( "<>" PGUID 0 b t f 30 30 16 644 649 0 0 oid8ne neqsel neqjoinsel ));
>
> points to a nonexistent operator --- there is no oid8ne in pg_proc, nor
> in the code... anyone feel like fixing it?
Added.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-10-29 18:17:59 | Re: [HACKERS] Open 6.4 items |
Previous Message | D'Arcy J.M. Cain | 1998-10-29 18:01:56 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/include/catalog pg_operator.h' |