followup to SELECT/INSERT problem

ok, so i decided to run a test with just the one element of my pipeline.

the process does:

BEGIN WORK;
loop
read stdin
if changes
UPDATE table1 SET ... WHERE KEY = ...;
print to stdout
END WORK;

now i fire up:
$ cat file.dat | adjust-rec > /dev/null

it works fine until the first update, then the backend goes into UPDATE and
starts eating CPU.

it appears that each call to UPDATE seems to be taking a long, long time to
complete.

--
[ Jim Mercer jim(at)reptiles(dot)org +1 416 410-5633 ]
[ Reptilian Research -- Longer Life through Colder Blood ]
[ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ]