Re: dblink_exists

From: ml(at)ft-c(dot)de
To: pgsql-sql(at)lists(dot)postgresql(dot)org
Subject: Re: dblink_exists
Date: 2020-12-21 05:07:57
Message-ID: 6963b9cb4034bb716fca2df60f3af69a08b395fd.camel@ft-c.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Sun, 2020-12-20 at 18:52 -0700, David G. Johnston wrote:
> On Sunday, December 20, 2020, <ml(at)ft-c(dot)de> wrote:
> >
> > My general problem:
> > I need a command that send a answer immediately and not, when the
> > query
> > if finished. 
> dblink_exec()?
  no, it needs a connection string
>  
> >
> > When someone start the script again (when it is running), so I need
> > a
> > section like:
> Advisory locks?
lock on a table: it is the  best solution  
> >
> > 2. question:
> > When dlink_send_query is running,
> > select dblink_get_connections()
> > send NULL as answer.
> >
> Don’t know - though suggest showing actual code that results in this
> behavior.

Franz

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Thomas Kellerer 2020-12-21 09:43:18 JSON path query returns duplicate values
Previous Message David G. Johnston 2020-12-21 01:52:04 Re: dblink_exists