<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Not even a little… I really would like to have some kind of “solution” to the problem of extra flag space the 3D people need, even if I don’t end up touching the overall serialization beyond that.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 21, 2019, at 9:18 AM, Regina Obe <<a href="mailto:lr@pcorp.us" class="">lr@pcorp.us</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Are we ready for a PostGIS 3.0 beta 1release?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Any more features we plan to put in 3.0 before we nail the box?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I’d like to package a PostGIS 3.0 beta 1 to go with the PostgreSQL 12 beta 1 as I see PostgreSQL 12 now shipping with PostGIS 2.5.2<span class="Apple-converted-space"> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">which is discouraging given the effort we’ve put in to take advantage of PostgreSQL 12 features with 3.0.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">relevant thread on IRC:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:42]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">Myon</span>> trying postgis on PG12beta1:<span class="Apple-converted-space"> </span><a href="https://pgdgbuild.dus.dg-i.net/job/postgis-binaries-beta/architecture=amd64,distribution=sid/35/console" target="_blank" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://pgdgbuild.dus.dg-i.net/job/postgis-binaries-beta/architecture=amd64,distribution=sid/35/console</a><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:42]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">sigq</span>> Title: postgis-binaries-beta » amd64,sid<span class="Apple-converted-space"> </span><span class="hyperlink-channel">#35</span><span class="Apple-converted-space"> </span>Console [Jenkins] (at<span class="Apple-converted-space"> </span><a href="http://pgdgbuild.dus.dg-i.net/" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">pgdgbuild.dus.dg-i.net</a>)<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:42]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">Myon</span>> is that a PostGIS problem, or one in PostgreSQL? (timestamp 17:39:21)<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:43]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">robe2</span>> Myon you should be using PostGIS 3.0 for 12<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:43]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">Myon</span>> well that doesn't exist yet<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:43]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">robe2</span>> Myon if we shipped a beta would that help?<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:43]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">robe2</span>> We are planning to release PostGIS 3.0 around same time as 12<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:44]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">robe2</span>> because it has a lot of stuff just for 12 :)<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:44]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">Myon</span>> a beta would help sortish, because I wouldn't want to ship to users before it's stable, while still trying to support PG12<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:45]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">Myon</span>> it's just these extra "WARNING: stats for "t.g" do not exist" lines, the rest of the tests works<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:45]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">Myon</span>> does it make sense that these are duplicated now, or is that something that should be fixed in PostgreSQL itself? (I haven't yet read any postgis code)<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="timestamp"><span style="font-family: "Courier New";" class="">[11:45]<span class="Apple-converted-space"> </span></span></span><span style="font-family: "Courier New";" class=""><<span class="hyperlink-whois">robe2</span>> Okay let me bring it up for discussion on postgis dev<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-family: "Courier New";" class=""></span><span style="font-size: 12pt; font-family: "Courier New";" class=""><robe2> we aren't testing PostgreSQL 12 on 2.5 -- so it may not work completely until release time as we won't be in a rush to fix issues on 12 in 2.5 until release<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 12pt; font-family: "Courier New";" class="">[11:46] <robe2> and the most we'd promise is it compiles -- not necessarily it regresses<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 12pt; font-family: "Courier New";" class="">[11:48] <Algunenano> About the duplicated messages, I think that the issue had to do with CTEs and robe2 fixed it in 3.0 and refushed (:D) to fixed it in 2.5<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 12pt; font-family: "Courier New";" class="">[11:50] <robe2> :D) yap I refused we didn't put in all this effort in 3.0 for 12 just to have people shipping 2.5 with 12<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-family: "Courier New";" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">If we aren’t ready maybe we should just wait till PG 13 comes out and forgo the 3.0 release in September. As there is no point in shipping a 3.0 mid cycle after PostgreSQL 12 is released and if packagers are going to ship a 2.5. Everyone will be settled in on a 2.5 and won’t waste their time upgrading to a 3.0 even if packagers were willing to ship a 3.0 with 12, which most WILL NOT.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thanks,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Regina<o:p class=""></o:p></div></div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">postgis-devel mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="mailto:postgis-devel@lists.osgeo.org" style="color: rgb(149, 79, 114); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">postgis-devel@lists.osgeo.org</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" style="color: rgb(149, 79, 114); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a></div></blockquote></div><br class=""></body></html>