From: | Jeremy Finzel <finzelj(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Segmentation Fault in logical decoding get/peek API |
Date: | 2019-02-14 22:42:04 |
Message-ID: | CAMa1XUiPZVyxYe2FTr4RVd8DPrb-h1_2CLBG1ND82wKk4eSvPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Feb 14, 2019 at 4:26 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> jfinzel <finzelj(at)gmail(dot)com> writes:
>
> You'd have to provide some evidence that that commit actually had
> something to do with a user-visible problem. It certainly wouldn't,
> by itself, have completely fixed any problem: at best it'd have
> transformed it from a crash into an elog(ERROR). More to the point,
> that commit was intended to silence a probably-hypothetical-anyway
> warning about the prior commit, so it wasn't fixing any issue that
> ever saw the light of day in a PG release.
>
And indeed I have not seen such error messages so I suspect you are right
there.
> So my bet is that your problem was fixed by some other commit between
> 10.3 and 10.6. Maybe the predecessor one, b767b3f2e; but hard to say
> without more investigation than seems warranted, if the bug's gone.
>
> regards, tom lane
>
I am willing to put in more time debugging this because we want to know
which clusters are actually susceptible to the bug. Any suggestions to
proceed are welcome.
Thanks,
Jeremy
From | Date | Subject | |
---|---|---|---|
Next Message | John Klann | 2019-02-14 22:52:14 | Re: BUG #15636: PostgreSQL 11.1 pg_basebackup backup to a CIFS destination throws fsync error at end of backup |
Previous Message | Peter Geoghegan | 2019-02-14 22:28:54 | Re: Segmentation Fault in logical decoding get/peek API |