Someone recently tweeted about the fantastic news that MySQL fixed a bug.
Now in my world, bugs get fixed quickly and well. Bugs happen and they need to be fixed. It never occurred to me that we should ever tweet or blog about the fixing of a bug. I guess I assume it's just quality: bugs get fixed, no drama - people depend upon us to do just that so that the (literally) millions of PostgreSQL servers out there run well. That's our job and I'm happy and proud to do that job alongside my colleagues at 2ndQuadrant and my colleagues in other PostgreSQL companies and in the wider community.
So the bug in question was "number 199"... check this out
It's always been a big argument in the PostgreSQL community about whether we need a bug tracker
We recently hosted the London PostgreSQL Meetup at a new location in Covent Garden. Room was great and its about 100m from Leicester Square tube, so very centrally located and easy to get to.
I've been the organizer of the group for more than 6 years now, in my role as the PostgreSQL Project's UK Press representative, though a few others have also helped out, principally Bart Swedrowski, though now also Sam Marshall. Anybody interested in PostgreSQL is welcome to come along and we have many speakers from a variety of companies and types of company. Please come along and join in with the other 849 members.
At our recent meeting we discussed all the new features of PostgreSQL 10. Lots of interest in the new SCRAM authentication
Postgres-BDR is an open source project from 2ndQuadrant that provides multi-master features for PostgreSQL. We have pursued a joint strategy of providing both working code available now and also submitting the features into core PostgreSQL.
Postgres-BDR 1.0 runs on a variant distro of PG9.4. This is in Production now and receives regular maintenance and security updates. 2ndQuadrant will support this until 9.4 End of Life in December 2019.
One of the greatest achievements to come out of our work on BDR is the logical replication technology. Our engineers spent a considerable amount of energy to contribute the tech to PostgreSQL core and I feel especially proud that this is a headline feature of the upcoming PG10 release.
And Now BDR 2.0 …
BDR 2.0 runs on community PG9.6 as
Some years ago, I prophesized that PostgreSQL would win in the end, and that we would be able to tell because there would be "Microsoft PostgreSQL".
I am happy to report that has now happened. Microsoft PostgreSQL database service on Azure was announced recently.
Of course, that was just a metaphor for "a.n.other big company", I'm not signalling MS as requiring special attention here, in fact they have been the last to do this.
That means PostgreSQL database services are now available from all of the main cloud service providers: Amazon, Google, IBM and Microsoft. Yay! We have achieved 100% breakthrough in terms of cloud adoption - everyone recognizes now that PostgreSQL is big and adoption is accelerating.
PostgreSQL is now used in UK and US governments, see UK (http://www.
Great conference! Paris is a great venue for travellers across Europe and worldwide. PgDay Paris 2017 was held in English and attracted a wide audience from many other countries: UK, NL, CH, BE, US, SE - and that was just the people I spoke to.
Je suis desolee ne parler ou ecrit pas en francais. Je suis un developpeur seulement.
I spoke in English about the new features in PostgreSQL 10 regarding Replication & Recovery. All very well received by a large technical audience. Logical replication, physical replication improvements, quorum commit, replication lag measurement and a ton of fine detailed improvements.
No slides, sorry. Come to the conferences! Meet people, hear their stories and share yours.
I travelled to Paris through London on a day of public murders that made news
GitLab, thanks for using PostgreSQL 9.6 and its replication and backup facilities.
We're sorry that you lost your database:
Thank you for posting this publicly to allow us to comment on this for your postmortem analysis.
I'm very happy that you monitor Replication Lag, that is good. Replication lag of 4GB is at times normal, so shouldn't have caused major concern. I've recently fixed a bug in replication that caused replication to hang in some cases for up to a minute; we released a public fix to that and it will be included in the next maintenance release of PostgreSQL 9.6. It's not certain that the bug was hit and, if it was, whether that was enough to cause the slow down noted. The openness of your response
Reading mailing lists can damage your health, as I recently discovered on the PostgreSQL Performance list where backup was being discussed.
First off, don't read blogs for finding out critical pieces of info. Read the docs because they are accurate, fully reviewed and well maintained.
I should add that I was the initial author of them as well, so maybe it's OK to carry on reading...
pg_start_backup() is a function we execute to start a base backup. It was part of the original API for physical backup introduced in PostgreSQL 8.0. It's now been mostly superceded by the replication command BASE_BACKUP, which is most frequently executed by the pg_basebackup utility.
So what does a base backup actually do? Well, first we execute a checkpoint so that as many changed data blocks are
Mirror mirror on the wall,
Who is the fairest Database of all?
A frequently asked question, certainly.
DB-Engines recently announced it's DBMS of the Year. Maybe the cool thing is that PostgreSQL is in 3rd Place. Yee-ha, an open source project is up there!
Let's look closely about what this means.
PostgreSQL.org's agreed response was this...
"It's great to see the continued success of PostgreSQL being reflected in DB-Engines rankings. It's clear that the strength of the following for the World's Most Advanced Open Source Database is enough to outweigh the largest software companies as people continue to choose to move away from commercial databases."
though because of commercial sensitivity this was toned down to this
"It's great to see the continued success of PostgreSQL
CHAR(16) Conference was a live conference in NYC held on 6 Dec 2016, focusing on Scalability for Business.
The Speaker Panel was recorded, so you can find out what happened here: https://youtu.be/eLjBoZr4dTc (1 hour)
Eric David Benari hosted an hour long "chat show" format, featuring
Other videos? No, sorry. Obviously, if you have to pay to attend, but we post the videos for free, then fewer people will attend. So next time please come along for the conference and find out what's happening, ask questions and enjoy chatting with the attendees.
Hope to see you next year
CHAR(16) Conference on Scalability for Business went very well in the heart of New York City.
Hotel Pennsylvania was a great venue; convenient for travel and a great conference venue with coffee, food and evening drinks.
Jonathan Katz was great as MC for the conference, while Eric David Benari did a great job of hosting the Speaker Panel and keeping everybody on their toes with surprising and revealing questions. We'll be posting the video for that sometime soon.
All the presentations were well received and the room was full all day long. Corridor feedback was that the speakers were good and the content was "dense" and very much in line with the specialised nature of the conference. Many good detailed questions after each talk, always a good sign people are tuned in.