Re: [WIP] plpgsql is not translate-aware

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: [WIP] plpgsql is not translate-aware
Date: 2008-10-09 00:22:42
Message-ID: 2107.1223511762@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> Another way, which would save some amount of string constant space,
>> is to have both elog_finish and the ereport macro pass NULL, and let
>> errstart insert the default:

> Hmm, true. I think this means we need to redefine ereport(), not just
> TEXTDOMAIN, in each module (in fact it makes TEXTDOMAIN goes away as a
> symbol). Same number of lines on each module though, so it's not a
> considerable difference.

No, you could have TEXTDOMAIN be defined as NULL by default, and let
modules redefine it as "foo".

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-10-09 00:36:31 Re: [WIP] plpgsql is not translate-aware
Previous Message Alvaro Herrera 2008-10-09 00:06:04 Re: [WIP] plpgsql is not translate-aware