Re: BUG #15734: Walsender process crashing when executing SHOW ALL;

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: cyberdemn(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15734: Walsender process crashing when executing SHOW ALL;
Date: 2019-04-11 03:07:12
Message-ID: 20190411030712.GH2728@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Apr 10, 2019 at 11:01:21AM -0400, Alvaro Herrera wrote:
> I think we should have a few tests issuing SHOW ALL in a replication
> connection with various levels of privilege; it's annoying that this bug
> took two years to find. With that, special-purpose buildfarm members
> would tell us if we've made some mistake in transaction handling or
> whatever.

What do you think about the set attached? I prefer that we use
psql(on_error_die => 1) so as in the case of a crash or an error the
test dies hard and fast. In consequence, I have granted
pg_read_all_settings to the replication user to ensure that no errors
happen, still the syscache lookup is done. We could have negative
tests but I don't think that's worth the addition as we already have
tests for pg_read_all_settings in src/test/regress/. If I remove the
patched patch from walsender.c, the test fails immediately.
--
Michael

Attachment Content-Type Size
wal-sender-show-v2.patch text/x-diff 3.4 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2019-04-11 03:26:31 Re: Suspicious strcmp() in src/backend/parser/parse_expr.c
Previous Message Michael Paquier 2019-04-11 02:19:46 Re: Suspicious strcmp() in src/backend/parser/parse_expr.c