| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: mcvstats serialization code is still shy of a load |
| Date: | 2019-07-05 17:36:39 |
| Message-ID: | 20190705173639.GA358@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Jul-05, Tom Lane wrote:
> FWIW, I don't think there's a need for every catversion on the back branch
> to look older than any catversion on HEAD. The requirement so far as the
> core code is concerned is only for non-equality. Now, extension code does
> often do something like "if catversion >= xxx", but in practice they're
> only concerned about numbers used by released versions.
pg_upgrade also uses >= catversion comparison for a couple of things. I
don't think it affects this case, but it's worth keeping in mind.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2019-07-05 17:38:26 | Re: range_agg |
| Previous Message | Julien Rouhaud | 2019-07-05 17:25:41 | Re: Add parallelism and glibc dependent only options to reindexdb |