From: | "Thomas Rosenstein" <thomas(dot)rosenstein(at)creamfinance(dot)com> |
---|---|
To: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Craig Ringer" <craig(at)2ndquadrant(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Logical Replication and triggers |
Date: | 2017-11-21 21:13:16 |
Message-ID: | 1D104B7E-9BEC-45F6-8D50-313249D2A35C@creamfinance.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Tue, Nov 21, 2017 at 3:29 PM, Simon Riggs <simon(at)2ndquadrant(dot)com>
> wrote:
>>> 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?
>
> That's not exactly how I read Craig's email, but it's of course
> difficult to know what tone somebody intended from an email. Suffice
> it to say that I think "please pay attention to this proposed bug-fix
> patch" is a pretty legitimate request.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
To weigh in here, I actually find it's a big hurdle
I'm a postgres user and not a postgres dev, so I definitly have the
feeling I'm not qualified to answer if this really does what it's
intended todo.
Further more not beeing in the processes it will take me probably 2 - 3
hours (if I have time) to figure out everything I should do and how I
should do it,
somebody doing this regularly might take 5 minutes.
Yes it fixes my replication issues, yes it seems to work on the first
look, but what does it really do - no idea!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-11-21 21:15:46 | Re: [HACKERS] pgbench regression test failure |
Previous Message | Peter Geoghegan | 2017-11-21 21:07:45 | Re: [HACKERS] CLUSTER command progress monitor |