Re: Performance problems testing with Spamassassin 3.1.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Parker <parkerm(at)pobox(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Performance problems testing with Spamassassin 3.1.0
Date: 2005-08-01 04:42:30
Message-ID: 24578.1122871350@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Michael Parker <parkerm(at)pobox(dot)com> writes:
> The next hurdle, and I've just posted to the DBD::Pg list, is
> escaping/quoting the token strings.

If you're trying to write a bytea[] literal, I think the most reliable
way to write the individual bytes is
\\\\nnn
where nnn is *octal*. The idea here is:
* string literal parser takes off one level of backslashing,
leaving \\nnn
* array input parser takes off another level, leaving \nnn
* bytea input parser knows about backslashed octal values

Note it has to be 3 octal digits every time, no abbreviations.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2005-08-01 04:53:22 Re: Performance problems testing with Spamassassin 3.1.0
Previous Message Michael Parker 2005-08-01 04:04:49 Re: Performance problems testing with Spamassassin 3.1.0