Re: pg_control_init() bug

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Bossart, Nathan" <bossartn@amazon.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2019-12-10T22:46:48Z
Lists: pgsql-hackers
"Bossart, Nathan" <bossartn@amazon.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



Commits

  1. Fix tuple column count in pg_control_init().

  2. Remove configure --disable-float4-byval