DEV Community

Stephen Charles Weiss
Stephen Charles Weiss

Posted on • Originally published at on

Postgres Tuples Only

If you’re just learning how to use Postgres from the terminal (as I am), sometimes you click the wrong button and don’t know what it does, then later, you realize something’s not quite right but don’t know how to fix it.

That’s what happened recently when I accidentally turned tuples only on (\t).

When I queried a table, only the results printed - not the column headers.

So, when querying a user table, I got the following:

onething=> select * from users;
  1 | stephen | |
  2 | fake user | |
Enter fullscreen mode Exit fullscreen mode

It’s not a complicated table, and it’s test data - so I could put the pieces together, but I knew one day, I’d want to see the headers.

That’s when I found that I’d accidentally fat-fingered turning Tuples only on.

Once I reversed it:

db=> \t
Tuples only is off.
Enter fullscreen mode Exit fullscreen mode

My query produced the table headers as expected:

db=> select * from users;
 id | name | email | password
  1 | stephen | |
  2 | fake user | |
(2 rows)
Enter fullscreen mode Exit fullscreen mode

To see the full list of options us the \? option from the command line, but for more, you can see the documentation on the interactive terminal on the Postgres site.

And now I know about tuples only mode in Postgres! Won’t make that mistake again.

Top comments (2)

benjaminadk profile image

Funny. I just did this and thought....what did I just break? Worthwhile post sir.

beaumontyun profile image

Nice and short post that landed on top of google search, so useful to know what happened when I accidentally pressed \t and thought "oh shit, what is this...?"