| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Sudalai <sudalait2(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Segmentation Fault in logical decoding get/peek API |
| Date: | 2018-02-21 01:20:40 |
| Message-ID: | CAH2-WzkXxqtEH8CpUrpSewFfiZFqyjrhjQ1nLeYb_n-kR_uU0Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Feb 20, 2018 at 1:35 PM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> And if it's segfaulting, it has to mean specinsert is NULL. So either we
> never got REORDER_BUFFER_CHANGE_INTERNAL_SPEC_INSERT, or we threw it
> away in the "change_done" part. Seems strange in both cases.
>
> Sudalai, are you using speculative inserts in the transaction?
He means ON CONFLICT DO UPDATE. :-)
The speculative insertion case handling in reorderbuffer.c is likely
something that is hardly ever used, since speculative insertion
conflicts are presumably generally very rare. Though at the same time,
they're surely very common for certain workloads (such as my testing
script for ON CONFLICT DO UPDATE [1]).
[1] https://github.com/petergeoghegan/jjanes_upsert
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sudalai | 2018-02-21 07:18:58 | Re: Segmentation Fault in logical decoding get/peek API |
| Previous Message | Tom Lane | 2018-02-21 00:23:57 | Re: pg_upgrade and materialized views |