Re: Jeff Janes 2019-03-23 <CAMkU=1zRvU5x1TAQNiXZK4sgjw1-AyWaFWAosdo7qujB7n7ijQ@xxxxxxxxxxxxxx> > On Fri, Mar 22, 2019 at 8:04 AM Steve Atkins <steve@xxxxxxxxxxx> wrote: > > > On Mar 22, 2019, at 10:56 AM, Christian Henz <c.henz@xxxxxxxxxxxxxxxxxx> > > There's the BigSQL fork, which had at least some minimal support > > for 10. I've no idea whether it's had / needs anything for 11 > > I just installed BigSQL's v11 of the database to get the pgAdmin3 that > comes with it (I couldn't get the Windows installer to install just > pgAdmin, I had to take the entire server installation along with it) . > Even though it comes with v11, when you start it says it only supports up > to v10, and then gives a series of warnings about catalogs and system admin > functions not being as expected. Once you are past the warnings, it does > work at least on the surface, but I have to think some features aren't > going to work. The BigSQL pgadmin3 "LTS" thing is a giant marketing hoax. Their patch consists of 90% replacing the original logo with their own version. The rest is mostly more re-branding, and then a tiny fraction of the patch establishes compatibility with PostgreSQL 10.0. They fumbled the version check, so it will complain about incompatibilities if you run it against 10.1 or any later version. The Debian pgadmin3 package has patches that actually work, also available on apt.postgresql.org. I don't claim that it is "supporting" PG10/11 in the sense that it knows about all features, but all the warnings on startup are properly avoided. Some day, I should build RedHat/Windows packages from that and put them somewhere... https://salsa.debian.org/postgresql/pgadmin3/tree/master/debian/patches Christoph
