ReDiscovering PostgreSQL

Last few months I have re-entered the PostgreSQL domain. After 25 years of "simple oracle dba" it is time to expand my field.

Starting, hopefully, with a trip to St Petersburg to visit the PGday 2017.
(insert link)

More news later.


Comments

Post a Comment

Popular posts from this blog

Yugabyte Major Upgrade, p4: Actual Upgrade.

Image
TL;DR: Run the check and then upgrade the database in careful steps. All implemented by just replacing containers and running a few (scripted) commands.  Success!   (but I did pop some questions at the bottom) The upgrade was Plug and Play with containes, more or les... Background. After preparation (link), my cluster is ready for upgrade. My cluster looks like this: Notice three containers running the yb-master-processes, node2, node3 and node4. And another three containers running the yb-tserver processes, node5, node6 and node7 (see prep-steps in earlier blog p3). I can now follow the required sequence: a) upgrade masters, by replacing three containers. b) run the check and the catalog upgrade, using 1 of the new containers. c) upgrade tservers by replacing three containers. d) finalize the upgrade. And if so desired, I can also re-distribute the load over all six containers again. Replacing the first container, fast. I will use node2 to introduce the new software-vers...
Read more

yugabyte : Finding the data, in a truly Distributed Database

Image
 TL;DR: I dig deeper into yugabyte to find/verify how the various components work, and where the data is kept. I find, with a little digging, that the data is Indeed Distributed and Replicated. Nice! Background In a previous post, I did some RTFM and identified various components that make up a running yugabyte "universe" or a cluster. Now it is time to find the actual data, and explore some of the tools.  hidden-agenda, wishlist: I would really like to be able to "query" this data straight from psql or cql, but that would require additions by yugabyte similar to how postgres exposes its catalog. In a distributed  environment, this is more of a challenge than in a "monolith" where everything is nicely in 1 place. Setup and Tools My "cluster" consists of 4 to 6 nodes running in docker. The setup is described in an earlier blogpost, and was a good starting point. But by now I begin to see I might want to use specific nodes for master and for tserve...
Read more

Yugabyte Major Upgrade part-3: setup and preparation

Image
 [DRAFT] TL;DR: I managed to upgrade yugabyte from pg11 to pg15, using just the container images. This page describes the system and the preparations. Spoiler: Yes! worked. But feel free to use / comment / improve on this. Background. As described in earlier blogposts, I am in the process of upgrading a yugabyte RDBMS from one Major Version to the next. Insert link p1, and link p2... Previous posts describe the summary of steps (p1), and the background to some of my choices (p2).  Now let me describe how this system was built and prepared for upgrade. The next blog (p4) will contain the report of the actual upgrade. Setup: create the containers. Normally I try not to modify a given container-image. Depending on how "strict" you are in containerisation, I do break some of the rules. I took a container image from the official repository (link), but I modified the run-command.  My command notably allows me to issue a "yugabyted stop" without the container coming down. ...
Read more