Re: [HACKERS] [QUESTIONS] builtin lo_unlink(int4)? why int4 not oid?

> I've just tested this, and I get the same thing (on 6.3.2, and yesterdays
> CVS versions).
>
> lo_unlink should be defined with oid (which I thought was the case).
>
> A temporary way round is:
>
>     select lo_unlink(raster::int4) from image;
>
> Hackers: Is there any reason why it's defined as an int4?

Here is a patch for to make lo_unlink use oid, not int4.

---------------------------------------------------------------------------

Index: src/include/catalog/pg_proc.h
===================================================================
RCS file: /usr/local/cvsroot/pgsql/src/include/catalog/pg_proc.h,v
retrieving revision 1.59
diff -c -r1.59 pg_proc.h
*** pg_proc.h    1998/05/29 13:36:31    1.59
--- pg_proc.h    1998/06/13 20:23:49
***************
*** 1174,1180 ****
  DATA(insert OID = 963 (  close_lb           PGUID 11 f t f 2 f 600 "628 603" 100 0 10 100  foo bar ));
  DESCR("closest point to line on box");

! DATA(insert OID = 964 (  lo_unlink           PGUID 11 f t f 1 f  23 "23" 100 0 0 100    foo bar ));
  DESCR("large object unlink(delete)");
  DATA(insert OID = 972 (  regproctooid       PGUID 11 f t f 1 f  26 "24" 100 0 0 100    foo bar ));
  DESCR("get oid for regproc");
--- 1174,1180 ----
  DATA(insert OID = 963 (  close_lb           PGUID 11 f t f 2 f 600 "628 603" 100 0 10 100  foo bar ));
  DESCR("closest point to line on box");

! DATA(insert OID = 964 (  lo_unlink           PGUID 11 f t f 1 f  23 "26" 100 0 0 100    foo bar ));
  DESCR("large object unlink(delete)");
  DATA(insert OID = 972 (  regproctooid       PGUID 11 f t f 1 f  26 "24" 100 0 0 100    foo bar ));
  DESCR("get oid for regproc");


--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.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)