I’m doing a talk on Sept 13th at GTALUG GTALUG Sept 2016 where I’ll be talking on things new in PostgreSQL 9.5 (released in January 2016) and upcoming in 9.6.
Here’s a copy of the material…
PostgreSQL New Stuff
Hmmph. Google sent me a “nastygram” indicating that one of my blog entries had something suggestive of content injection.
I poked around, and it was by no means evident that it was really so. The one suspicious posting was http://linuxdatabases.info/blog/?p=99 which legitimately has some stuff that looks like labels, as it contains a bunch of sample SQL code. I’m suspicious that they’re accounting that as being evil…
But it pointed me at a couple of mostly-irritating things…
I had been lazy, leaving all alone.
In February, I figured I was heading off for a chunk of the month on a cruise, hence wanting tablet for multimedia, but without network, so it was timely not to spend time fiddling with configuration with possible risk of mussing such up.
Alas, the OTA upgrade to JellyBean did a certain chunk of mussing… It busted SuperUser access, thereby breaking Titanium Backup. No backups went properly since :-(.
So, today seemed right timing. I wanted backup, and needed root, the latter looking like a fight. Ah well, go for gusto, see what we get without it…
I had to upgrade adb to support latest Android… Got Clockwork Recovery in place, and zip files for CM10.1 and Google Apps…
The last backup was Feb 16, but happily the files still remained after fresh CM10.1 installation, so I could do a good chunk of recovery of apps, and in plenty of cases, this was basically network configuration, so apps would update their own data upon startup. Sweet!
Superuser is nicely integrated into CM10, also sweet, no extra installation process.
I’ll need to reconfigure the launcher, due to the shift from ADW (I had a license) to built-in Trebuchet on CM10, but that seems like the “worst” irritation, and one I can well live with.
I’m not sure I can readily identify big differences between stock Android and CM10, but there are nice small creature comforts my CM10 phone has gotten me used to, like a quick “turn on/off WiFi” directly on notification screens. Small but I like it.
As part of “due diligence” for some mailing lists I am involved with (for Slony, see slony-backups ), I discovered the need to dump out Mailman mailing list subscribers.
I’d kind of rather have something a bit more version-tracked, so I poked around at GitHub, and found larsks / mailman-subscribers
That was a little out of date; the last code was from a couple of years ago, so I forked, updated to the latest, and suggested that “larsks” pull it, which he did, quite quickly.
The “kudos” bit is that I noticed a bit of a blemish, in that the mailing list password was required to be on the command line, thereby making it visible to anyone with access to /usr/bin/ps on one’s system. I submitted a feature request, and Lars was so kind as to have this feature added so quickly that by the time I had the prototype of my Slony “subscriber backup” script working, I immediately needed to change it to make use of the lovely new password-in-file feature. Nice!
I happen to be a supporter of Joey Hess’ Git Annex Kickstarter project; no big bucks, but it seemed a good thing to help out.
I got in the stickers, that were my “project reward,” and figured I should start playing with the new results. I’m particularly keen on the planned Android client, but I should make some use of it before that comes available.
There’s good news, and bad news:
debian unstable, in a version released September 24th.
debian testing, and it has a version released July 24th, well before any of this, and without any of Joey’s recent enhancements.
Fortunately, drawing in the September/~unstable~ version isn’t too terribly difficult. My
/etc/apt/preferences.d/simple configuration has
Pin-Priority values that prefer
experimental (where enormous potential for breakage lies!).
As a consequence, installing the
testing version is pretty easy, albeit involving an option I had to go looking for:
root@cbbrowne:~# apt-get -t unstable install git-annex ... leads to loading ... Get:1 http://ftp.us.debian.org/debian/ unstable/main git-annex amd64 3.20120924 [7,411 kB]
And, with a run of
% git annex webapp, it’s up and running!
Worth observing… The documentation tree includes the entirety of Joey’s blog documenting his development efforts. Possibly excessive, but it’s certainly not to be called inadequate documentation.
To get this to work, you need…
It was created as a standard in 1999, and hasn’t been updated much since, so there are things that postdate it, and that are thus not supported.
I was a bit tickled by the characterization I saw today in the new Subversion release, describing the deprecation of version 1.5:
The Subversion 1.5.x line is no longer supported. This doesn't mean that your 1.5 installation is doomed; if it works well and is all you need, that's fine. "No longer supported" just means we've stopped accepting bug reports against 1.5.x versions, and will not make any more 1.5.x bugfix releases.
They aren’t telling us the world will end for anyone using version 1.5, just that they don’t intend to provide support anymore.
Which seems like a fine thing. Version 1.5 is 3 years old, and, when they seem to be releasing about a version per year (1.0 in 2004, 1.7 in 2011), 3 years of backwards support doesn’t seem dramatically insufficient. Particularly if, when support goes away, you’re not inherently doomed!
Making for some reasonably good news on 9/11, the next version of PostgreSQL, version 9.1, has been released.
Major enhancements include:
Many of these continue the trend of continuing to enhance features added in earlier versions (e.g. – synchronous replication, KNN, Writable CTEs)
Some introduce new kinds of functionality (e.g. – SE-Postgres, FDW, Extensions), where new seeds are sown, that we may expect to flower into further new features in future versions.
My latest “musical experiment” is with Clementine, which was recently added to Debian.
I should note things that I have used in the past, and some areas of past pain:
At any rate, I saw Clementine listed as “new in Debian,” so thought I’d take a peek. I’m liking what I see thus far:
Seems pretty likable thus far…
In July 2010, we switched over to use Git, which has been working out quite fine so far. The official repository is at git.postgresql.org; note that some developers are publishing their repositories publicly at GitHub:
You can find details at those “private” repositories of branches that the developers have opened to work on various bug fixes and features.
We have been working on what seems most likely to be called the “2.1 release.”
sl_log_*tables improve performance when undergoing large backlog
There are two features being worked on, which we hoped would be ready around the time of PGCon 2011:
SUBSCRIBE SETwould wait until the subscription has been completed before proceeding.
Unfortunately, neither of these are quite ready yet. It is conceivable that the automatic waiting may be mostly ready, but complications and interruptions have gotten in the way of completion of multinode failover.
Three possibilities seem to present themselves:
Implicit WAIT FOR EVENT, which would make for a substantially more featureful 2.1, and let
multinode FAIL OVERcome along later.We had been hoping that there would be common functionality between these two features, so had imagined it a bad idea to do one without the other. But perhaps that’s wrong, and
Implicit WAIT FOR EVENTdoesn’t need multinode failover to be meaningful. That does seem like it may be true.
There is still the same issue as with 1. above, that this would mean having an extra version of Slony to support, which isn’t something anyone is too keen on.
Development of the failover facility seems like it will be bottlenecked for a while on Jan, so this suggests that it may be timely to solicit features that Steve and I might work on concurrently in the interim.
But that is certainly not the only opinion out there – there are apparently others that regularly use them.
While I’m not keen on putting effort into them, if there is some consensus on what to do, I’d go along with it. That might include: