Attendees of PgConf.US , if you haven't gotten your hotel room booked, now is the time! Our block ends on March 6th. Point your browser over here and book that room. While you wait for your email confirmation from the Westin, you can take some time to review the following talk from PgConf US 2015, ToroDB: a new, open-source, document-oriented, JSON database, built on Postgres.
Seattle Postgres and People, Postgres, Data were present at the 20th Anniversary Event of LinuxFest Northwest this weekend! The “Fest” is a conference built around Free and Open Source Software, taking place in Bellingham, Washington. It is a true gathering of over 2000 Open Source practitioners. There was also a well attended Postgres Track and an “Ask the experts” panel.
Also at LinuxFest Northwest was YottaDB. YottaDB uses the PostgreSQL wire protocol to allow universal driver access to their in-memory transactional database. This has become a popular way to utilize the maturity of the PostgreSQL code base and reduce overhead in having to maintain a protocol and drivers.
What is high cardinality, and how do time-series databases like InfluxDB and TimescaleDB compare?
11 Things to Know about Databases and Postgres in Containers
PostgreSQL security: a quick look at authentication best practices [Tutorial]
Distributed PostgreSQL on a Google Spanner Like Architecture - Storage Layer
We are looking for good dates to host PostgresConf Philly in July/August 2019 and we are actively reviewing new markets for other Postgres Conference events including Texas, Vancouver B.C., and Seattle. If you have feedback on opportunities in these areaa including dates, venues, or a desire to join the amazing People, Postgres, Data team, let us know at organizers@postgresconf.org.
The PostgreSQL git repo was largely bug fixes and updates the past couple of weeks but we have some great releases including migration tools and Distributed SQL:
Yugabyte v1.2.4 (Apr 02, 2019), Distributed SQL
Postgres Checkup 1.0, Automate checking on Postgres health
PgCLI v2.1.0, A feature-full command line client for Postgres
People, Postgres, Data and The World’s Database
The World’s Database celebrates all of Postgres, including whichever version, fork, or hybrid used to build yourself, your business, or your hobby. We have Open and Closed Source technologies. We have amazing extensions (TimescaleDB), unique implementations (Yugabyte), and respected forks to solve specific problems such as Greenplum, Azure, and Aurora. We have meetups where professionals can gather to collaborate and network in all major U.S. markets. Most importantly we are an inclusive community celebrating everything surrounding the maturity, extensibility, and growth of the Postgres ecosystem.
As one of the Founders of United States PostgreSQL, a former Director of Software in the Public Interest (one of the NPOs behind Postgresql.org), a former committer (web), former major contributor, President of the oldest PostgreSQL company still independent in North America, and the Founder of Postgres Conference (in the U.S.), I thought I would offer a knowledgeable perspective.
I have had long discussions with one of the primary people within the Fundacion PostgreSQL (Alvaro) and his heart is in the best interest of the community, even if Postgresql.org, PGEU and PGCAC do not agree. You can see this demonstrated within Fundacion’s trademark policy. That said, Fundacion PostgreSQL did go about their actions in an incorrect way. There should have been an open discussion and they should have provided PGCAC the opportunity to resolve the trademark issues on their own. It is also true that while I believe PGEU and PGCAC believe they are protecting the community, if they were interested in positive community growth and collaboration, they would not be taking the approach they currently are. The current path has far reaching implications that PGEU and PGCAC do not see.
Further, the PostgreSQL Community Association of Canada and Fundacion PostgreSQL have resorted to terrible language in representing what is actually going on within the disagreement. Using language such as, “An attack on our community” or “PostgreSQL attacks the community” is immature at best and at worst an intentional decision to use good faith and mindshare against what is largely just a disagreement that could be solved with an active mediator and a few phone calls. If this disagreement is about the best interest of the PostgreSQL community, shouldn’t that involve discourse, honesty, transparency, and kind communication?
(1) Internet consulting.
(2) Internet presence provider- DNS hosting.
(3) Commercial internet support for database applications development and implementation including the ability to host internet domains (as an internet service provider) and provide a wide range of web site development, programming and information technology services, namely computer software architecture, design and/or development services.
(4) Computer hardware sales and service.
The solution to the whole problem is simple; a single contract that states:
The contract should not contain language in regards to future potential filings that involve but are not exclusive to the word Postgres or PostgreSQL. There are already a number of filings worldwide that use Postgres or PostgreSQL as part of an overall mark inclusively such as Postgres Pro, Postgres Plus, Postgres Always On and Postgres Enterprise Manager, all of which are not owned but PGCAC or PGEU.
Because it is the right thing to do. Otherwise this whole affair is going to end up costing one entity or another way too much money for no purpose. There is no clear distinction on who would legally win, and in either situation the main sufferers are the PostgreSQL community. Let’s have the parties show an act of kindness for the betterment of everyone involved.
On occasion, professional developers will drop into the Postgresql.org mailing lists, meetups, and conferences to ask the question, “Why isn’t PostgreSQL development on Github?” In an effort to see if the demand was really there and not just anecdotal we ran a poll/survey over several social media platforms that asked a simple question:
Should PostgreSQL development move to Github?
We received well over 300 responses and the majority (75%+) chose a move to Github or to something like Github. This was an unscientific poll but it does point out a few interesting topics for consideration:
This poll does not answer point #3; it only provides a data point that people may desire a modern collaboration platform. The key takeaway from the conversation about migrating to Github or similar service is the future generation of developers use technology such as Slack and Microsoft Teams. They expect a bug/issue tracker. They demand simplicity in collaboration and most importantly they will run a cost->benefit analysis to determine if the effort to contribute is a net positive.
It should also be considered that this is not just individual potential contributors. There are many corporations big and small that rely on the success of PostgreSQL. Those corporations will not contribute as much directly to PostgreSQL if the cost to benefit analysis is a net negative. They will instead contribute through other more productive means that produce a net positive when the cost->benefit analysis is run. A good example of this analysis is the proliferation of external projects such as pg_auto_failover, patroni and lack of direct contribution from innovative extension based companies.
There are those within the Postgresql.org community that would suggest that we do not need a culture shift within PostgreSQL but that does not take into account the very clear market dynamics that are driving the growth of PostgreSQL, Postgres, and the global ecosystem. It is true that 20 years of hard work by Postgresql.org started the growth and it is also true that the majority of growth in the ecosystem and community is from products such as Greenplum, Aurora, Azure, and Timescale. The growth in the ecosystem is from the professional community and that ecosystem will always perform a cost to benefit analysis before contributing.
It is not that we should create radical rifts or disrupt our culture. It is to say that we must evolve and shift our community thinking. We need to be able to consider the big picture. A discussion should never start as an opposition to change. The idea of change should be an open discussion about possibility and vision. It should always include whether the change is a good idea and it should always avoid visceral reactions of, "works for me,” “no,” or “we tried that 15 years ago." Those reactions are immature and lacking in the very thing the community needs to continue to grow: positivity, inclusion, vision, and inspiration.
As part of the countdown to PostgresConf US 2019, learn more about about featured Platinum Sponsor 2ndQuadrant, including their commitment to partnering with and contributing to the Postgres community.
Tell us about the recent uptick in Oracle to Postgres migrations.
Licensing costs of Oracle is a significant factor for businesses looking to migrate towards PostgreSQL. Not only is PostgreSQL a more cost effective solution, but it provides enterprise-level capabilities and customization options. The increasing demand for migration services from Oracle to PostgreSQL can also be attributed to the availability of PostgreSQL in the cloud.
Where do you see the Postgres market going?
PostgreSQL has been gaining traction with every release; interest and usage by large enterprises worldwide is growing exponentially due to the robust capabilities it provides. 2ndQuadrant intends to continue their active contributions in development and supports the overall growth of PostgreSQL.
Do you have any big wins this year?
2Q PGConf 2018 had a successful second year bringing together PostgreSQL developers and users. Both speakers and attendees enjoyed the combination of technical and use case topics as well as the diverse range of networking opportunities.
Sri Rangarajan, Lead Software Engineer at Enova International, commented saying he appreciates 2ndQuadrant’s hard work in “promoting and fostering a savvy, healthy and helpful community to welcome newcomers just like [it] did for [him] 5 years ago!”
For the second year in a row, PostgreSQL has been named DBMS of the Year by DB-Engines. This shows that developers and users alike are acknowledging the robust and versatile capabilities that it has to offer.
What is the number one benefit you see within Postgres that everyone should be aware of?
PostgreSQL's advanced features cater to a broad range of use cases all within the same DBMS. Rather than going for edge case solutions, developers are relying on the absolute reliability of the hyperconverged database to simplify their production deployments.
What is the best thing about working with the Postgres community?
The Postgres community is one of the easiest global communities to work with. There is an open mindset all around and a common goal of growing the Postgres ecosystem as a whole.
Tell us why you believe people should attend PostgresConf 2019 in March.
Conferences are a great way for people in the PostgreSQL community to come together and share knowledge and ideas, which is the true spirit of open source. It is very exciting to see into the future developments of the project from the people who contribute so much to its growth.
It is a great way for members of the community to come together in person to share knowledge in different areas of the technology, describe practical use cases, and give sneak previews into cutting edge technologies for future versions of PostgreSQL.
About 2ndQuadrant:
2ndQuadrant provides PostgreSQL Solutions for the Enterprise - reliably deploying them on the platform of your choice and providing 24/7 Production Support. Our solutions address all aspects of your database ecosystem, ensuring high availability, disaster recovery, backup & failover management, and much more.
Moreover, we provide tools to make your deployment process simple and reliable. With over 100 years of combined code contributions to the PostgreSQL project, our engineers ensure that your PostgreSQL solutions are fully supported in your production environment.
Visit the 2ndQuadrant team in the Exhibit Hall in the Metropolitan Ballroom on Wednesday, March 20, and Thursday, March 21.
Check out the full schedule for PostgresConf US 2019, and buy your tickets soon!
Henrietta Dombrovskaya, Diversity, Equity, and Inclusion member for PostgresConf as well as Chicago Postgresql organizer nominated for Technologist of the Year!
A large, well known media company is seeking a Senior Level PostgreSQL Engineer and Architect. This is an on-site engagement, however the company is known to be lifestyle friendly with reasonable working hours, good pay, and benefits. Specific talents requested are the ability to mentor. The location is Seattle, WA. If you are interested in this position please contact randy@neuringerco.com with your resume.
We wanted to highlight some of the fantastic work that is being done by the ecosystem with Postgres Extensions. Although the base of Postgres is the amazing and extensible PostgreSQL, a lot of users don’t realize that Postgres has the feature they are looking for, if only they were to look to the ecosystem.
pgaudit : The goal of pgAudit is to provide PostgreSQL users with the capability to produce audit logs often required to comply with government, financial, or ISO certifications.
pg_credereum : pg_credereum is a PostgreSQL extension that provides a cryptographically verifiable audit capability for a PostgreSQL database, bringing some properties of blockchain to relational DBMS.
H3-pg : PostgreSQL bindings for H3, a hierarchical hexagonal geospatial indexing system.
There are a ton of Postgres compatible features out there. Some of them are overlooked core features and some of them require installing a different version of Postgres. Here are a few examples:
TimescaleDB: Time series data management with Postgres
YugabyteDB: Globally Distributed database with PostgreSQL compatibility
Postgres-XL: Horizontally partitioned PostgreSQL
Agensgraph: Graph capabilities with Postgres
PG-Strom: GPU accelerated extension for Postgres
