If you’re running Manjaro Linux on ThinkPad and you tried to update your system recently, you might have run into this problem. I encountered it with a ThinkPad T420s and a ThinkPad P50 both running Manjaro-i3.

Using zip and tar to compress files and directories can take up a lot of your time. Many times, DevOps CI/CD pipelines involve zipping the artifact build the build stage, then deploying and unzipping the artifact once it is copied to its destination. There are several such Jenkins to AWS pipelines that I work with where this is the case: * build and zip the artifact * move the artifact to ec2 instances * unzip the artifact on ec2 instance * run post-deployment steps, etc This is fairly common in modern software engineering. You may be or probably are running…

In this article, we will walk through a very real scenario in which renaming some PostgreSQL Databases on the primary of a primary, replica database server pair caused replication streaming to get “Ugly.”

Problem

I was responsible for several well-spec’d Linux database machines serving hundreds of thousands of users in a production environment. Linux OS: RHEL 7 on bare metal Postgresql version: 10.4 I was restoring 3 databases from a separate primary, second server pair running RHEL 6 and Postgresql version 9.3. The pg_restore attempts were all successful, then I decided I wanted to rename the databases. After running “ALTER DATABASE…

Why is my archive/ directory on my Centos 7 Postgresql 10.4 installation several hundred GibiBytes?

First of all, “GibiBytes,” you may ask. Yes. It’s what Centos and perhaps Unix in general uses for file sizes. It’s just 2³⁰ bytes, whereas GB or GigaBytes is 10⁹ bytes. Now that we have that behind us:

Are you noticing the archive/ directory size getting out of hand?
You’ll probably notice that archive_mode is set to on by default.

### Here is what the Archiving section of the postgresql.conf file looks like by default:# - Archiving -archive_mode = on              # enables archiving; off, on, or always
                                # (change requires restart)archive_command = 'cp %p /var/lib/pgsql/10/archive/%f' # command…

Let’s start by making sure we understand how to backup a whole Postgresql database using pg_dump.

-- execute a pg_dump as root
# pg_dump -U postgres -Fc source-db-name > /directory/path/db-dump-name.dump

• pg_dump invokes the utility.
• -U postgres switches the command to be run as the postgres user.
• -Fc puts the resulting file into a format that can be restored from.
• > outputs the command to the singular dump file.
• The synopsis from the official documentation is:
  pg_dump [connection-option...] [option...] [dbname]

Now, Let’s make sure we understand how to create a new blank database instance to restore into.

-- first switch to postgres user # su - postgres -- invoke psql interactive terminal $ psql -- then create a…

I’m working on CentOS 7 and Postgresql 10, both fully patched at time of writing. That said, the process of backing up and restoring postgres databases is the same between the version 9.3 systems that I interact with.

First we have to connect to the server that is hosting the database instance that we want to backup. Here’s an example of the process one might go through.

1. Connect to VPN

I’m using vpnc to connect to a dedicated firewall (Adaptive Security Appliance), and I’ve designed a config file located in /etc/vpnc/ I can invoke with this command:

$ sudo vpnc rsvpn

If you’re…

All as root as performed on two onMetal Cloud I/Ov2 instances at RackSpace with rackconnect networking to get these well spec’d instances behind our primary dedicated firewall.
For some licensing reason, Red Hat doesn’t allow RHEL licenses to these onMetal servers. So, it was a good excuse to use CentOS instead. So far, seems to be the same deal practically speaking.

1. add necessary repo

# rpm -Uvh https://yum.postgresql.org/10/redhat/rhel-7-x86_64/pgdg-centos10-10-2.noarch.rpm

There is a yum version of this farther down. The above command assumes Centos 7 is your operating system. …

TL;DR

-- because sometimes you're not just going from Windows to Linux :-)
you're going from Linux to Linux, and that's cool

if == input file
of == output file
usage example:
$ sudo dd status=progress if=name-of.iso of=/dev/sdb

This assumes you already have an ISO file that you want to move to an external “thumb drive” type of USB storage volume; but if not, head on over to: https://manjaro.org/ where you’ll find the loveliest ISO grabbing experience of your life. Here you get to “Choose an Edition.” Personally, I would steer you towards the i3 version:
“DOWNLOAD I3 EDITION.” …