Polarity Reference Channels: PostgreSQL Error Codes

Polarity User Tips - Jun 26, 2020

Polarity Reference Channels: PostgreSQL Error Codes cover image

Today’s post continues an ongoing series on Polarity User Tips. Data tells a story, Polarity helps you see it with Augmented Reality overlaying contextual information as you work, giving you the right data at the right time to make informed decisions and take action with speed (no glasses or goggles required). This guide explains how you can see the story in your data with Polarity using the PostgreSQL Error Codes Reference Channel.

Intro to Polarity Reference Channels

Polarity Channels are a way to organize Entities and Annotations into logical groups, such as all of your assets or your LinkedIn contacts.

Reference channels are a Polarity Channel that is based on another source of information that is used just for reference purposes by Polarity Users. Reference channels can be anything from a list of internal or external threats to a list of assets to the PostgreSQL Error Codes list.

Where to find Reference Channels

On the Polarity Github page, download the PostgreSQL Error Codes reference channel or browse our library of reference channels for better data awareness and recall.

What are PostgreSQL Error Codes?

The PostgreSQL Error Codes is a list of codes that help database users troubleshoot what is happening within the database. The codes range from things that help with queries that are causing issues to errors that have occurred when the database crashes.

PostgreSQL Error Codes Reference Channels in Polarity

Based on the list that Postgres publishes, we have put together a CSV that you can easily upload into Polarity as a reference channel. The reference channel will instantly map the error codes that Postgres provides to what the error code is allowing you to easily correct what is happening.

For example, when you are troubleshooting inside a virtual machine and see something on your screen like “42601” in the image below, you immediately have awareness of what the errors mean, allowing you to course-correct what you are working on without ever having to leave the terminal.

In this image, notice the highlighted error codes 42P01, 42703, or 42601 on the left. You can see that Polarity’s computer vision recognized the text on screen, and in real-time while the analyst is working, it has provided contextual information from the PostgreSQL Error Code Reference Channel in the overlay window on the right.

What Next?

Tune into our next Community Tech Tuesday to learn more. Not a Polarity user? See for yourself with a Polarity demo or trial, or take the Tour.