Hi!
On Mon, Dec 31, 2018 at 2:58 AM Peter J. Holzer wrote:
> On 2018-12-30 08:56:13 -0800, Adrian Klaver wrote:
> > On 12/30/18 3:08 AM, Peter J. Holzer wrote:
> > > If I understood Mitar correctly he wants the trigger to execute in the
> > > session where it was declared, not in the sessio
Hi!
On Sun, Dec 30, 2018 at 9:58 PM David G. Johnston
wrote:
> Doesn’t seem likely. Maybe you can use NOTIFY/LISTEN in your temporary
> triggers and have your active client perform the work after being notified.
Yes, this is what I ended up doing. I signal the client and then the
client
On 2018-12-30 08:56:13 -0800, Adrian Klaver wrote:
> On 12/30/18 3:08 AM, Peter J. Holzer wrote:
> > If I understood Mitar correctly he wants the trigger to execute in the
> > session where it was declared, not in the sessio where the statement was
> > executed that triggered the trigger.
>
>
On Friday, December 28, 2018, Mitar wrote:
>
> On Fri, Dec 28, 2018 at 9:36 PM Adrian Klaver
> wrote:
> > When you create the temporary function it is 'pinned' to a particular
> > session/pg_temp_nn. Running the trigger in another session 'pins' it to
> > that session and it is not able to see
On 12/30/18 3:08 AM, Peter J. Holzer wrote:
On 2018-12-29 13:01:47 -0800, Adrian Klaver wrote:
On 12/28/18 11:44 PM, Mitar wrote:
On Fri, Dec 28, 2018 at 9:36 PM Adrian Klaver wrote:
When you create the temporary function it is 'pinned' to a particular
session/pg_temp_nn. Running the trigger
On 2018-12-29 13:01:47 -0800, Adrian Klaver wrote:
> On 12/28/18 11:44 PM, Mitar wrote:
> > On Fri, Dec 28, 2018 at 9:36 PM Adrian Klaver
> > wrote:
> > > When you create the temporary function it is 'pinned' to a particular
> > > session/pg_temp_nn. Running the trigger in another session 'pins'
On 12/28/18 11:44 PM, Mitar wrote:
Hi!
On Fri, Dec 28, 2018 at 9:36 PM Adrian Klaver wrote:
When you create the temporary function it is 'pinned' to a particular
session/pg_temp_nn. Running the trigger in another session 'pins' it to
that session and it is not able to see the posts_temp table
Hi!
On Fri, Dec 28, 2018 at 9:36 PM Adrian Klaver wrote:
> When you create the temporary function it is 'pinned' to a particular
> session/pg_temp_nn. Running the trigger in another session 'pins' it to
> that session and it is not able to see the posts_temp table in the
> original session.
On 12/28/18 7:56 PM, Mitar wrote:
Hi!
On Fri, Dec 28, 2018 at 3:25 PM Adrian Klaver wrote:
Sure, but why is a temporary function used as a temporary trigger made
There is no such thing as a temporary trigger.
A trigger defined using a temporary function gets deleted once a
function gets
Hi!
On Fri, Dec 28, 2018 at 3:25 PM Adrian Klaver wrote:
> > Sure, but why is a temporary function used as a temporary trigger made
>
> There is no such thing as a temporary trigger.
A trigger defined using a temporary function gets deleted once a
function gets deleted, which is at the end of
On 12/28/18 12:59 PM, Mitar wrote:
Hi!
On Fri, Dec 28, 2018 at 12:57 PM Adrian Klaver
wrote:
CREATE OR REPLACE FUNCTION pg_temp.my_function()
And it does what?
Copies/transforms data from posts into posts_temp.
When a row is added to "posts" table outside of my session, function
Hi!
On Fri, Dec 28, 2018 at 12:57 PM Adrian Klaver
wrote:
> > CREATE OR REPLACE FUNCTION pg_temp.my_function()
>
> And it does what?
Copies/transforms data from posts into posts_temp.
> > When a row is added to "posts" table outside of my session, function
> > "my_function" is called, but it
On 12/28/18 12:47 PM, Mitar wrote:
Hi!
It seems to me that triggers on a table are run in the session context
of the user who made a change in the table, but not of the user who
defined the trigger?
So I create a temporary function:
CREATE OR REPLACE FUNCTION pg_temp.my_function()
And it
Hi!
It seems to me that triggers on a table are run in the session context
of the user who made a change in the table, but not of the user who
defined the trigger?
So I create a temporary function:
CREATE OR REPLACE FUNCTION pg_temp.my_function()
And a temporary table:
CREATE TEMPORARY TABLE
14 matches
Mail list logo