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

Re: Transactional issue that begs for explanation

From: Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Transactional issue that begs for explanation
Date: 2010-09-11 03:32:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
Tom Lane wrote:
> I suspect you're shooting yourself in the foot by repeatedly re-opening
> the backend's stdout and not fflush'ing anywhere along the line: somehow
> the data going to the log file is getting mangled.  I don't see any
> strange behavior here when using a less dangerous logging technique,
> such as
> $key=$_TD->{old}{key};
> $val=$_TD->{old}{val};
> elog(NOTICE, "Firing on: $key $val\n");
> return;
> $$ LANGUAGE plperlu;
> (Actually, I don't see anything funny when using your original version
> of the function, either; but it's probably dependent on a lot of
> platform-specific libc details exactly how you got that result.)
> 			regards, tom lane
Tom, you are a great guy. I didn't know about the elog function, I've 
just tried to re-invent the wheel. Thanks for the pointer, I will try 
with elog. Actually, I was trying to check what from the following 
article is applicable to Postgres:

What I did figure out is
a) Postgres doesn't restart the transaction the same way that Oracle 
does or the trigger would fire twice.
b) There is no DBMS_OUTPUT, so I tried to re-invent the wheel.

I  still don't know what does Postgres do when the data in a block 
needed by current transaction changes the value? Oracle simply restarts 
the transaction, in order to have a clean slate.

Mladen Gogala 
Sr. Oracle DBA
1500 Broadway
New York, NY 10036
(212) 329-5251 

In response to


pgsql-novice by date

Next:From: Thomas KellererDate: 2010-09-11 06:54:01
Subject: Re: Transactional issue that begs for explanation
Previous:From: Tom LaneDate: 2010-09-11 02:23:04
Subject: Re: Transactional issue that begs for explanation

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