> That's what I did at first, but later I found better performance with
> a TRIGGER on the permanent table that deletes the target of an UPDATE,
> if any, before the UPDATE. [INSERT!] That's what PG does anyway, and now I can do
> the entire UPDATE [INSERT] in one command.
It's probably obvious, but what I should have said is that now I do the INSERT in one command; I have no need of an UPDATE. So I do no UPDATEs, only INSERTs.
pgsql-performance by date
|Next:||From: James Mansion||Date: 2007-12-16 22:24:01|
|Subject: Re: libgcc double-free, backend won't die|
|Previous:||From: Usama Dar||Date: 2007-12-16 20:33:58|
|Subject: Re: Large Objects and Toast|