Yes it's the "performance issue".
I am going to talk to them about the triggers tomorrow.
On the other hand I would still like to know if it is possible to do it by
modifying the execMain.c or nodeModifyTable.c files?
And also what about fast path interface? Is it possible to use it instead?
--
Yes I have tried it with triggers but I have to do it without using triggers.
Since in my workplace someone has already done that and for some reason (may
be because triggers are expensive i suppose...not sure though), hence they
want me to do it by modifying the source code.
--
View this message
Is it possible to modify source code in executor to keep a log of old tuples
and new tuples after an UPDATE, INSERT or DELETE command is executed? (so
basically Store Old Tuple Values -> UPDATE/INSERT/DELETE Command -> Store
New Tuple Values)
For example is it possible to modify the execMain.c fi
Well what i mean by print out is that it should print out the old and new
tuples on postgres terminal after the update is complete.
I tried it with triggers and I got what I wanted. But my professor for some
reason wants me to mess around with the source code :(
Do you think it's possible?
--
Hello there,
I am a total novice to Postgresql, but very much interested in learning how
it works.
I have to modify the source code of Postgresql-9.0.1 such that whenever I
run an UPDATE command it should print out the old and new tuples. Since I am
a beginner I would appreciate it a lot if anyo
Hello there,
I am a total novice to Postgresql, but very much interested in learning how
it works.
I have to modify the source code of Postgresql-9.0.1 such that whenever I
run an UPDATE command it should print out the old and new tuples. Since I am
a beginner I would appreciate it a lot if anyo
