| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Fix a crash in logical replication |
| Date: | 2019-01-30 09:54:33 |
| Message-ID: | 201901300954.7jrbodhjkgmm@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-01-30 10:31:39 | pgsql: Fix a crash in logical replication |
| Previous Message | Michael Meskes | 2019-01-30 09:39:44 | pgsql: Make sure that ecpglib's statement variable has a defined value |