Re: plperl failure on OS X 10.5(.1)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: "B(dot) Maust" <bmaust(at)u(dot)washington(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: plperl failure on OS X 10.5(.1)
Date: 2007-11-21 16:39:14
Message-ID: 11826.1195663154@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Nothing fatal? Huh, you have a curious idea about warnings. This makes
> me think you have the wrong headers or something -- the argument
> mentioned in all these cases is bool, so maybe there is an ABI
> incompatibility somewhere.

Yeah, and it's hardly difficult to see how that might lead to the
reported "null prosrc" error, either.

bool isnull;
...
prosrcdatum = SysCacheGetAttr(PROCOID, procTup,
Anum_pg_proc_prosrc, &isnull);
if (isnull)
elog(ERROR, "null prosrc");

> Perhaps a Perl header is redefining "bool" on your platform?

Seems the question is not so much about OS X as it is about what
perl you're using ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-11-21 16:42:46 Re: Postgres 8.3 archive_command
Previous Message Matteo Beccati 2007-11-21 16:30:37 Re: Better default_statistics_target