| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: PDF build issue with 9.0 Alpha5 |
| Date: | 2010-04-02 20:10:26 |
| Message-ID: | 3466.1270239026@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
I wrote:
> For an actual fix, it looks like we have got three alternatives:
> * find out what's chewing up so many strings and get rid of it.
Some tracing suggests that there may indeed be a single culprit that we
could fix or nuke. Practically all of the string pool is consumed by
strings like these:
x(at)116714
p(at)116714
x(at)116715
p(at)116715
x(at)116718
p(at)116718
x(at)116719
p(at)116719
x(at)116720
p(at)116720
x(at)116721
p(at)116721
x(at)116722
p(at)116722
These are presumably names of TeX control sequences, but I haven't found
what's defining them.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-04-02 21:34:49 | Re: PDF build issue with 9.0 Alpha5 |
| Previous Message | Erik Rijkers | 2010-04-02 19:50:05 | Re: PDF build issue with 9.0 Alpha5 |