| From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
|---|---|
| To: | Viktor Holmberg <v(at)viktorh(dot)net> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ON CONFLICT DO SELECT (take 3) |
| Date: | 2025-11-19 17:19:35 |
| Message-ID: | CAEZATCVtzJj1yns64eiNu3tf4fgUiDkKhF-T8c5DY=9veuk4rw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 19 Nov 2025 at 16:51, Viktor Holmberg <v(at)viktorh(dot)net> wrote:
>
> For the CASE default, elog(ERROR, "unrecognized LockClauseStrength %d” that was removed.
> Would this now trigger a compile time error/warning? And are you supposed to get 0 warnings when compiling?
That shouldn't trigger a warning, because there is a case block for
every enum element, and yes there should be 0 compiler warnings.
> (I get a large amount of warnings "warning: 'pg_restrict' macro redefined" on master, but that could just be something with my environment)
I haven't seen that before, but there's this thread:
If you re-run configure, does it go away?
Regards,
Dean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-11-19 17:23:01 | Re: RFC: Logging plan of the running query |
| Previous Message | Álvaro Herrera | 2025-11-19 17:07:16 | Re: PRI?64 vs Visual Studio (2022) |