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

Re: [HACKERS] regproc fix

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart)
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] regproc fix
Date: 1998-10-02 15:00:19
Message-ID: 199810021500.LAA05915@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
> > One remaining problem is that you have to supply the oid in quotes,
> > because regproc has to get a string, not an int.  Perhaps we need
> > another regprocin that allows int4 or char*, but I don't think you can
> > allow two input functions for a type.
> > 
> > Perhaps we can just leave it.  We also output the proname, even if 
> > they used the oid as input.
> 
> The int4 vs. string issue would be easily solved by having a routine
> regproc(int4), which the new type coersion stuff would use
> automatically.

I started coding it, but realized that things like CREATE FUNCTION will
still be looking for a string for the input function, so we would have
to change those too.  Does not seem worth the confusion.

-- 
  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


In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-10-02 15:22:27
Subject: Re: [HACKERS] spinlock code for ns32k (again)
Previous:From: Bruce MomjianDate: 1998-10-02 14:47:16
Subject: Re: [HACKERS] Open 6.4 items

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