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

Re: BUG #4443: Dblink wrong output on trigger

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jose Manuel Mira" <labsig(dot)iug(at)ua(dot)es>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4443: Dblink wrong output on trigger
Date: 2008-09-30 12:31:24
Message-ID: 8306.1222777884@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Jose Manuel Mira" <labsig(dot)iug(at)ua(dot)es> writes:
> If we open manually a connection (with this sentence: 
> select dblink_connect('conexion','dbname=XXX user=XXX password=XXX
> host=localhost') ) the trigger must show a notice that there are open
> connections and proceed to close it. The trigger never evaluates this
> condition and proceeds to insert a row, not taking into account that there
> are open connections with the same name.

You didn't show exactly what you did and what result you got.  I tried
the function and trigger and they seem to work as expected here.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: SantoshDate: 2008-09-30 12:36:12
Subject: BUG #4445: Atomic transaction problem
Previous:From: Dmitry OrlovDate: 2008-09-30 10:29:08
Subject: BUG #4444: Wrong formated pdf manual

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