<div>I agree with Anthony. it will be great.</div><div> </div><div>28.10.2016, 15:33, "Anthony DeBarros"
<adebarros@gmail.com>:</div><blockquotetype="cite"><div>While pgAdmin 4 will naturally continue to improve, it is
fullyunderstandable that people want to keep pgAdmin3 alive and are willing to do the work. That's the beauty of open
source.However, I'm wondering whether it would make sense for the community to agree on maintaining one fork of the
projectso that various improvements all end up in the same place?<div> </div><div>For example, yesterday BigSQL
announcedits own fork of pgAdmin3:</div><div><a
href="https://www.bigsql.org/pgadmin3/">https://www.bigsql.org/pgadmin3/</a></div></div><div> <div>OnFri, Oct 28, 2016
at3:16 AM, Dmitry Voronin <span><<a href="mailto:carriingfate92@yandex.ru"
target="_blank">carriingfate92@yandex.ru</a>></span>wrote:<blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc
solid;padding-left:1ex;">Hello,<br/><br />For some reasons we need to use pgadmin3 in our work. I will make some fixes
ofpgadmin3 origin code to make it useable with new PostgreSQL versions.<br /><br />My fork located at: <a
href="https://github.com/dimv36/pgadmin3"target="_blank">https://github.com/dimv36/pgadmin3</a>.<br /><br />Today
pgadmin3can:<br /><br /> - Create or edit policies<br /> - Enable/Disable RLS on tables.<br /> - Full translation
forru locale.<br /><br />Your pull requests or additions are welcome!<br /><br /><span><font color="#888888">-- <br
/>Bestregards, Dmitry Voronin<br /><br /><br />--<br />Sent via pgadmin-support mailing list (<a
href="mailto:pgadmin-support@postgresql.org">pgadmin-support@postgresql.org</a>)<br/>To make changes to your
subscription:<br/><a href="http://www.postgresql.org/mailpref/pgadmin-support"
target="_blank">http://www.postgresql.org/mailpref/pgadmin-support</a></font></span></blockquote></div></div></blockquote><div> </div><div> </div><div>-- </div><div>Best
regards,Dmitry Voronin</div><div> </div>