| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Solaris compiler status |
| Date: | 2025-09-03 11:42:56 |
| Message-ID: | F6DEB4F0-E2B2-4CB7-9E0A-A791B5268CBA@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 3 Sep 2025, at 07:47, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> - Hundreds of compiler warnings (They are not necessarily wrong, but it shows that no one has taken care to tune the warnings or the code in any way recently.)
Should these be posted somewhere before they are lost in case anyone is keen on
digging through the list for any relevant fixes?
> So, can we declare that we don't support this compiler anymore?
>
> (gcc is readily available and seems to work alright, so I'm not saying the OS is no longer viable.)
+1 based on the findings above.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2025-09-03 11:50:09 | Re: pg_restore --no-policies should not restore policies' comment |
| Previous Message | Zhijie Hou (Fujitsu) | 2025-09-03 11:40:53 | RE: pgsql: Preserve conflict-relevant data during logical replication. |