We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

How Postgres Got Its Groove Back (Part 2)

00:00

Formale Metadaten

Titel
How Postgres Got Its Groove Back (Part 2)
Serientitel
Anzahl der Teile
25
Autor
Mitwirkende
Lizenz
CC-Namensnennung - keine kommerzielle Nutzung - Weitergabe unter gleichen Bedingungen 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache
ProduktionsortOttawa, Canada

Inhaltliche Metadaten

Fachgebiet
Genre
InternetworkingData Encryption StandardManagementinformationssystemBaum <Mathematik>ProgrammierumgebungJust-in-Time-CompilerZustandsdichteGroße VereinheitlichungDifferenteSoftwaretestSoundverarbeitungWort <Informatik>ZahlenbereichStatistische HypotheseMultiplikationsoperatorRuhmasseSkriptspracheFortsetzung <Mathematik>DruckspannungFlächeninhaltVersionsverwaltungFunktionalInformationsüberlastungProzess <Informatik>Projektive EbeneData MiningOpen SourceMathematikTexteditorTermDatenbankComputerunterstützte ÜbersetzungCodeMaßerweiterungDatenstrukturForcingDivergente ReiheCASE <Informatik>Dreiecksfreier GraphArithmetisches MittelSystemverwaltungSoftwareschwachstelleWeb-SeiteAbfrageOrakel <Informatik>Rechter WinkelSpeicherabzugSelbst organisierendes SystemVererbungshierarchieLesezeichen <Internet>SoftwareEinfügungsdämpfungDruckverlaufRichtungQuick-SortKreisflächeExistenzsatzJSON
Transkript: Englisch(automatisch erzeugt)
Longo is perfectly pitched and perfectly positioned for that audience. They're accustomed to thinking in JSON. They're accustomed to thinking in those data structures. And Postgres, it's still kind of bolted on and on the side and not 100% supported. But I believe that that's surmountable in a number of different ways. At the back.
So the big difference with Afghanistan. We have to be Afghanistan, not France. Sorry, no offense.
France has an incredibly ferocious army and a long history of beating up its neighbors. In America, that's not well known. But I mean, the answer, I'm being quite serious. If you fight people on their own turf, you'll lose, right? If Postgres goes out there and starts taking all the dimes we can scrape together
and tries to buy a Super Bowl ad, it's not going to work. The way to compete with someone is not to go to their strengths. It's to go to their weaknesses. We have an enormous community. We can build a community. People don't hate us. That's an asset.
And people want us to succeed because everybody hates Oracle. I look to my colleagues at Salesforce and the great work that they're doing. They're doing that because this open source project exists. And regardless of whether all of that code gets back, they are supporting and contributing to this community,
and not just through hiring people, which, by the way, they're hiring if you are interested in joining a really amazing and awesome database project. So sorry, just to repeat the question,
you were saying that if you think about it in terms of Linux versus FreeBSD, then maybe the Postgres versus, well, I don't know who I would compare with. I mean, the competition Mongo has a massive marketing budget. The competition MySQL had a massive marketing budget. These were commercial companies. I think we can continue to be competitive with them
by using different tactics. How do we argue against?
So if you're looking for a company,
sort of the one throat to choke principle this is known as in some circles. The question was, how do you get Postgres into places where people want a company that will provide support? And there are a number of answers in this room. Heroku is a subsidiary of Salesforce, and EnterpriseDB has been doing this forever.
So if you're talking about that, I mean, well, another answer is that you
don't have to win all the fights, go to where the enemy is weak. If those kinds of organizations, there are lots of organizations in Europe using Postgres today, and there are lots of people who
are willing to make the trade-offs because they get so many other advantages. I saw a question over here. OK. Yeah, David?
What do I think the front page should look like? I think it should look like a series of AB tests, which look at actual data rather than my half-assed, three-in-the-morning opinion made in MS Paint. But in all honesty, it doesn't matter
what I think it should look like. I think that the way to improve it is to have somebody come up with a small change, a small hypothesis, run an AB test, and see what the effect is. You measure it, you iterate, you improve over time. It's just like building any other software. Yes, Jager?
Yes. So the question was, PostGIS is an amazing tool,
and Postgres is much stronger than the competition in geospatial things. But as an extension, it's not well integrated. How do we address that? I think the answer is actually not to pull things into the core. That just makes it slower. It puts it on the same release cycle as Postgres.
It means more people with more code that can break. The answer is actually to improve the extension functionality. It's to get PostGIS into PGXN, get tools into Postgres that allow you to query and install things straight from PGXN inside the database, and to make that experience transparent and seamless and dependable. And then that way, installing Postgres
isn't some crazy process involving like installing 15 different weird versions of Debian packages and then like running some Perl script, which 80% of the time, it works all the time. But it's actually like this well-supported, very smooth and slick experience. And we've seen real strides in that direction recently,
and I think we need to continue to invest there. Yes. Yes. The comment was that we could get more people into the funnel
if we had better GUI tools. psql is really, really awesome as a command line tool. And I bet you most of the people who develop on Postgres and most of the people in this room, if they have a query to write, they go to that. And backslash e, if you don't know, opens your favorite text editor and lets you edit a query in it.
You're right. GUI tools are a great example of one of those cases where less skilled users feel a lot of pain that more skilled users don't. pgAdmin is out there. It's been around forever. It serves some of that need. NaviCAD is out there. It's commercial, but I hear good things about it.
We're seeing other open source tools starting to try and add functionality in that area. SQL Pro is a famous MySQL one. They've been getting so much pressure on them lately to adopt Postgres that they've actually started working towards that. We'll see if it materializes. I think maybe I have time for one last question and then we'll call it.
Anyone? All right, well thanks.