| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Fix a crash in logical replication |
| Date: | 2019-01-30 13:47:08 |
| Message-ID: | 34cf0db4-62e3-63b1-576c-310b785a877f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 30/01/2019 10:54, Alvaro Herrera wrote:
> On 2019-Jan-30, Peter Eisentraut wrote:
>
>> Fix a crash in logical replication
>>
>> The bug was that determining which columns are part of the replica
>> identity index using RelationGetIndexAttrBitmap() would run
>> eval_const_expressions() on index expressions and predicates across
>> all indexes of the table, which in turn might require a snapshot, but
>> there wasn't one set, so it crashes. There were actually two separate
>> bugs, one on the publisher and one on the subscriber.
>
> The intention is to backpatch this fix all the way back to 9.4, right?
Yeah, the backpatching took a little longer than expected.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-01-30 17:52:04 | Re: pgsql: Change error handling of out of scope variables in ecpg. |
| Previous Message | Michael Meskes | 2019-01-30 13:37:55 | pgsql: Change error handling of out of scope variables in ecpg. |