| From: | Dave Page <dave(dot)page(at)enterprisedb(dot)com> |
|---|---|
| To: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org>, pgadmin-hackers <pgadmin-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Greenplum support |
| Date: | 2020-04-17 10:08:16 |
| Message-ID: | CA+OCxowB54V4QDOS_fvAd=Ljh79Ej7cHyfUXLwt70NGRAB2JZg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers pgadmin-support |
All,
pgAdmin has tried to support Greenplum for many years, albeit
semi-unofficially. For many years Pivotal (who maintain Greenplum) were
supporting that effort, however for the last 1-2 years that support has
vanished.
None of the current maintainers of pgAdmin are able to support Greenplum,
so unless someone is able to step up and work on that, I don't believe we
have any choice but to drop support entirely rather than leading users to
think it's supported and then to run into issues.
Is there anyone willing to step up and work on the Greenplum issues that
are currently known, and others that may come up in the future?
[image: Screenshot 2020-04-17 at 11.07.41.png]
--
Dave Page
VP & Chief Architect, Database Infrastructure
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amol Vyavahare | 2020-04-17 10:18:58 | Re: [pgAdmin][RM4946] Issue with temporary tables on commit drop as. |
| Previous Message | Akshay Joshi | 2020-04-17 09:21:43 | Re: [pgAdmin4][RM#3495] Do not check for binary content if BOM marker is present in the file |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nagaraj Raj | 2020-04-17 20:11:34 | pgAdmin is freezing |
| Previous Message | Michael Benjamin | 2020-04-16 15:41:27 | Re: Export Error |