Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
> I've been thinking some more about the long-standing problem of the
> AFTER TRIGGER queue using too much memory, and I think that the
> situation can be improved by using some basic compression.
> Currently each event added to the AFTER TRIGGER queue uses 10 bytes
> per trigger per row for INSERTs and DELETEs, and 16 for UPDATEs. The
> attached patch reduces this down to just 1 byte in a number of common
Ummm ... I only read the data structure comments, not the code, but I
don't see where you store the second CTID for an update event?
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Dean Rasheed||Date: 2011-08-01 17:00:00|
|Subject: Re: Compressing the AFTER TRIGGER queue|
|Previous:||From: Joshua D. Drake||Date: 2011-08-01 16:42:01|
|Subject: PgWest CFP extended for 12 days|