Re: [WIP] plpgsql is not translate-aware - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [WIP] plpgsql is not translate-aware
Date
Msg-id 20081008235310.GK4164@alvh.no-ip.org
Whole thread Raw
In response to Re: [WIP] plpgsql is not translate-aware  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [WIP] plpgsql is not translate-aware
Re: [WIP] plpgsql is not translate-aware
List pgsql-hackers
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:
>
> > +     edata->domain = domain ? domain : "postgres";
>
> Otherwise we'll have at least one copy of "postgres" per backend .o
> file ...

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.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: WITH RECURSIVE ... simplified syntax?
Next
From: Alvaro Herrera
Date:
Subject: Re: [WIP] plpgsql is not translate-aware