| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Unbreak the build. |
| Date: | 2022-03-23 15:38:39 |
| Message-ID: | CA+TgmoandqPXmJt5JGq3zhNg4geUv0ruj9C8P+gRY3+z50CPww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Mar 23, 2022 at 10:46 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> There's new warnings that sound reasonable introduced in the prior commit that didn't get removed in this one:
>
> https://cirrus-ci.com/task/5259487073271808?logs=mingw_cross_warning#L392
That link takes me to a screen that shows no warnings. Scrolling
around the only thing I see that doesn't seem to be addressed by this
commit is a complaint about get_bc_algorithm_name falling off the end.
I've added a dummy return statement to hopefully address that.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-03-23 15:48:18 | pgsql: test_decoding: Add comments about delaying BEGIN/PREPARE |
| Previous Message | Robert Haas | 2022-03-23 15:38:08 | pgsql: In get_bc_algorithm_name, add a dummy return statement. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-23 15:43:17 | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |
| Previous Message | Dilip Kumar | 2022-03-23 15:35:09 | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |