* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> dblink connections to your own database are very seldom a good idea;
> there is always a better, more efficient, less deadlock-prone way
> to do it. In this case I'd venture that you want to use a SECURITY
> DEFINER function, and not dblink at all.
The one case I've seen where people are trying to do this is where they
want to provide some kind of notification or log to a table to be
visible prior to the current transaction actually committing. I can see
how this could be useful for long-running transactions or function calls
(It'd actually be useful in some of the work I've been doing, but we've
worked around it by providing NOTICE's when we're debugging and
splitting the long running function into multiple function calls when we
want more fine-grained information about where we're at in the process
for users to view).
Thanks,
Stephen
