Tom Lane wrote:

> But why do you need your own xlogging at all?  Shouldn't these actions
> be perfectly ordinary updates of the relevant catalog tuples?

The XLog entry can be smaller, AFAICT (we need to store the whole new
tuple in a heap_update, right?).  If that's not a worthy goal I'll
gladly rewrite this piece of code.

Ah, there's another reason, and it's that I'm rewriting the tuple in
place, not calling heap_update.  I'm not sure if I can reuse
log_heap_update for this purpose -- I'll take a look.

Alvaro Herrera                      
The PostgreSQL Company - Command Prompt, Inc.

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Reply via email to