| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Update SQL conformance information |
| Date: | 2019-08-22 19:56:39 |
| Message-ID: | 72bb5436-f328-d321-db34-29d19f33bd18@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 2019-08-22 15:56, Tom Lane wrote:
> Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
>> Update SQL conformance information
>> T612 has been fully supported since the major window function
>> enhancements in PostgreSQL 11, but it wasn't updated at the time.
>
> So shouldn't that get back-patched into 11 and 12?
We usually don't update these in released branches, since it changes the
catalog contents. We could possibly do it in 12 if we have other
catalog changes pending.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-08-22 20:39:51 | pgsql: Fixes for "Glyph not available" warnings from FOP |
| Previous Message | Tom Lane | 2019-08-22 13:56:37 | Re: pgsql: Update SQL conformance information |