Re: get_database_name() from background worker

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: ROS Didier <didier(dot)ros(at)edf(dot)fr>
Cc: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>, Koichi Suzuki <koichi(at)2ndquadrant(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: get_database_name() from background worker
Date: 2019-12-13 05:01:24
Message-ID: CAMsr+YESe0cPfmg2pX7YvHiQL=K0LAMXQqsPeNK_2QQ814fe4A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 12 Dec 2019 at 16:21, ROS Didier <didier(dot)ros(at)edf(dot)fr> wrote:

> Hi
> With pg_background extension ,it is possible to make "autonomous
> transaction" which means possibility to commit in a transaction.
> It is like a client which connects to a postgresql instance. So you can
> execute any sql orders .
>
>
Yes, that's possible. It's not easy though and I strongly suggest you look
into existing approaches like using dblink instead.

Please start a new thread rather than following an unrelated existing one.

--
Craig Ringer http://www.2ndQuadrant.com/
2ndQuadrant - PostgreSQL Solutions for the Enterprise

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2019-12-13 05:05:41 Re: xact_start for walsender & logical decoding not updated
Previous Message Thomas Munro 2019-12-13 04:41:56 Re: checkpointer: PANIC: could not fsync file: No such file or directory