Re: Logical Replication and triggers

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Thomas Rosenstein <thomas(dot)rosenstein(at)creamfinance(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Logical Replication and triggers
Date: 2017-11-21 20:29:48
Message-ID: CANP8+j+-tb6Nv_89fqKBuV7fq+ggYUeOnNY3HgcNYBZYgtnSFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21 November 2017 at 13:27, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sat, Nov 18, 2017 at 7:30 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>> On 15 November 2017 at 21:12, Thomas Rosenstein
>> <thomas(dot)rosenstein(at)creamfinance(dot)com> wrote:
>>> I would like somebody to consider Petr Jelineks patch for worker.c from
>>> here
>>> (https://www.postgresql.org/message-id/619c557d-93e6-1833-1692-b010b176ff77%402ndquadrant.com)
>>>
>>> I'm was facing the same issue with 10.1 and BEFORE INSERT OR UPDATE
>>> triggers.
>>
>> Please:
>>
>> - Apply it to current HEAD
>> - Test its functionality
>> - Report back on the patch thread
>> - Update the commitfest app with your results and sign on as a reviewer
>> - If you're able, read over the patch and make any comments you can
>>
>> "Somebody" needs to be you, if you want this functionality.
>
> You realize we're talking about a bug fix, right? And for a feature
> that was developed and committed by your colleagues?

Craig is asking Thomas to confirm the proposed bug fix works. How is
this not normal?

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-11-21 20:39:32 Re: Logical Replication and triggers
Previous Message Ildus K 2017-11-21 20:28:55 Re: [HACKERS] Custom compression methods