Re: [HACKERS] Names that suddenly include an OID

> There's been a very recent change to include the OID in certain names
> in the system table. Do a "select * from pg_amop;" to see what I
> mean: the values for amopselect and amopnpages didn't have the OID
> appended before. Was this change intentional? If so, I'm really
> curious as to why... And what's the best way to find out, from SQL,
> that 'btreesel' should now be 'btreesel_1268'?

OK, it was me who added it, and it still has some problems. The reason
the oid was added is that the old code just displayed the
pg_proc.proname for regproc fields, and the input function just found
the FIRST function with a matching name, which is a problem because we
can have multiple functions with the same name but different types.

You can input into regproc with the name_oid format, or you can just
give it the oid.

The problem is that certain function create items now have problems, as
outlined in the e-mails I am attaching, and am still looking for
suggestions on this. I can put it back to the old way too.

--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)