Re: pg_control_init() bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_control_init() bug
Date: 2019-12-10 22:46:48
Message-ID: 16584.1576018008@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Bossart, Nathan" <bossartn(at)amazon(dot)com> writes:
> I noticed that pg_control_init() is failing an assertion on 13devel:

Hmm, yeah. In a non-assert build I get

regression=# select * from pg_control_init();
ERROR: function return row and query-specified return row do not match
DETAIL: Returned row contains 12 attributes, but query expects 11.

> The attached patch seems to clear this up. I think this was missed in
> 2e4db241.

Evidently. Thanks for the report!

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Finnerty 2019-12-10 22:50:29 Re: On disable_cost
Previous Message Andres Freund 2019-12-10 22:37:16 Re: xact_start for walsender & logical decoding not updated