Skip site navigation (1) Skip section navigation (2)

Re: Compressing the AFTER TRIGGER queue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Compressing the AFTER TRIGGER queue
Date: 2011-08-01 16:49:08
Message-ID: 24460.1312217348@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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
> cases.

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

Responses

pgsql-hackers by date

Next:From: Dean RasheedDate: 2011-08-01 17:00:00
Subject: Re: Compressing the AFTER TRIGGER queue
Previous:From: Joshua D. DrakeDate: 2011-08-01 16:42:01
Subject: PgWest CFP extended for 12 days

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group