Re: zeros in oidvector type

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: zeros in oidvector type
Date: 2000-01-11 11:36:42
Message-ID: 200001111136.GAA04436@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom, why are the non-trailing zeros in the *vector types as initialized
> > in the catalog/*.h files.
>
> > You mentioned you knew what they meant.
>
> In pg_proc's proargtypes entries, a zero in a valid argument position
> (ie, one of the first 'pronargs' positions) can mean either "any type
> is acceptable" or "opaque argument type" (not sure if those are quite
> the same thing or not!) or "C string input to a datatype's typinput
> conversion routine" (definitely not the same thing).
>
> The entries in pg_proc.h call out these zeroes explicitly even when
> they are trailing arguments --- generally, the number of values shown
> in the proargtypes column should equal pronargs.

The reason I ask is that there are some parts of the code that try to
find the number of args by looking for the _first_ non-zero entry in the
list. I changed those to look for the _last_ non-zero entry, but it
sounds like that is still wrong.

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-01-11 13:26:42 Re: [SQL] createdb -D xxxx not working
Previous Message Mateus Cordeiro Inssa 2000-01-11 10:45:51 Re: [HACKERS] Simmultanous Connections (fwd)