pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Parker <parkerm@pobox.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance problems testing with Spamassassin 3.1.0
Date: Mon, 01 Aug 2005 00:42:30 -0400
Message-ID: <24578.1122871350@sss.pgh.pa.us> (raw)
In-Reply-To: <20050801040443.GA6527@mail.herk.net>
References: <42E80C28.2040608@aptalaska.net>
	<1122532023.25574.1.camel@localhost.localdomain>
	<42E9749F.6000709@aptalaska.net>
	<1122616211.5691.340.camel@lamb.mcmillan.net.nz>
	<42EA6966.8090402@aptalaska.net>
	<1122668371.5691.352.camel@lamb.mcmillan.net.nz>
	<19405.1122670917@sss.pgh.pa.us>
	<42EAA410.9010700@aptalaska.net>
	<27897.1122748133@sss.pgh.pa.us>
	<20050801040443.GA6527@mail.herk.net>

Michael Parker <parkerm@pobox.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



view thread (62+ messages)  latest in thread

Message-ID: <24578.1122871350@sss.pgh.pa.us>
Permalink:  ../24578.1122871350@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24578.1122871350@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, parkerm@pobox.com
  Subject: Re: Performance problems testing with Spamassassin 3.1.0
  In-Reply-To: <24578.1122871350@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox