| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <akapila(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Remove unused wait events. |
| Date: | 2021-10-25 17:39:44 |
| Message-ID: | 4052153.1635183584@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> Since this will cause integer values to have different textual enum value
> representations in 14 and 15+, do we want to skip two numbers by assigning the
> next wait event the integer value of WAIT_EVENT_WAL_WRITE incremented by three?
> Or enum integer reuse not something we guarantee against across major versions?
We require a recompile across major versions. I don't see a reason why
this particular enum needs more stability than any other one.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-10-25 18:01:22 | Re: pgsql: Remove unused wait events. |
| Previous Message | Daniel Gustafsson | 2021-10-25 17:34:37 | Re: pgsql: Remove unused wait events. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2021-10-25 17:43:18 | Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT. |
| Previous Message | Daniel Gustafsson | 2021-10-25 17:34:37 | Re: pgsql: Remove unused wait events. |