1. 19

At the heart of Postage is a modern, fast, event-based C-binary, built in the style of NGINX and Node.js. As such, even though it’s still early days, Postage is as fast as any PostgreSQL interface can hope to be (which just happens to be a lot faster than PGAdmin3).

http://www.meetup.com/austinpug/events/230328766/

http://github.com/nunziotocci/postage

  1.  

  2. 9

    The fancy JS on the website for that slide in effect is something I could live without.

    Nice work though!

    1. 3

      We have now removed the animations on our postage landing page. Thank you.

    2. 7

      Just checked out the repo. Looks like lots of work has gone into it already. Very cool to read about an alternative.

      Can you guys add some screenshots to the website please?

      1. 4

        added! thank you for the suggestion!

        see screenshots

        1. 2

          Hey Justin, The screenshots look good. Love the explain graph and the object dependencies graph. These should be very handy.

          1. 2

            <gs-img class="image-id-1" style="background-image: url(&quot;images/ScreenShot1.png&quot;);" src="images/ScreenShot1.png" min-width="all {247px,200px}; sml {507px,409px};"></gs-img>

            What’s gs-img? These don’t seem to be backwards compatible with the standard img tag, and cannot be viewed without CSS, it looks like. (Even with CSS, they’re scaled down, and aren’t very accessible.) I think it’s best to use the standard img, and make the images be links to themselves for easier viewing/zooming.

            1. 2

              <gs-img> is a web component. You are absolutely right, those should click through. We’ll add that. Thank you for the suggestion.

              1. 2

                I made it so that the images zoom when you click on them (you may need to refresh the page). Thanks for the feedback.

                1. 1

                  that didn’t really work as well as hoped so now if you click on an image it just opens the image in a new tab.

          2. 5

            I visited several of the links in this story but I could not understand what makes pgAdmin a pain point with postgresql. Now, I’m mostly a MS SQL Server user and so I relate pgAdmin to MS SQL Server Management Studio.

            1. 4

              The original impetus was to bring it to a web page so that we could fix stuff while at customer sites. Often we’d walk up to a computer for the first time (we’re mostly remote) and have to install PGAdmin3 to start working.

              We suspected that we could build something faster than our fifteen year old competitor, but even we were shocked at how much faster remote access is when using LibPq and a C binary. Once we saw the speed difference in our testing we were full speed ahead on building it.

              We have autocomplete and can handle 20000 tables easy without scrolling speed issues (or crashing like PgAdmin).

              Our datasheet view allows arbitrary selection with copy and paste, for example, you can select a few columns a few records down and paste over them. The copy and paste functionality is very rich.

              Also, having a web client gives you more deployment options. We typically install it on our dev boxes but you could install Postage on the same server as your database. It doesn’t require a separate web server. It doesn’t require any config change to put it behind Nginx or Apache in a reverse proxy either, though you’d probably want to turn off SSL on the web side if it’s on the same box as the web server. It’s pretty slick.

              1. 1

                They are solving the problem of pgadmin not being node.js Web Scale.

              2. 1

                I really wish there was a way to favorite things on lobste.rs

                1. 1

                  Michael and Nunzio put together a map that shows Postage users across the world…

                  http://www.workflowproducts.com/postage.html