If you manage PostgreSQL from a terminal you already know Beneath that familiar surface, though, Below are six of the most useful commands\u2014features even experienced users often overlook\u2014along with practical examples of when they shine.<\/p>\n When you need a real-time view of something\u2014queue depth, lock counts, job status\u2014 The query runs once, then automatically re-executes every five seconds, clearing and rewriting the output in place. It\u2019s the quickest way to turn a one-off query into a minimalist dashboard while you\u2019re troubleshooting or demoing.<\/p>\n Tip:<\/em> You can direct Long rows wrap badly in narrow terminals. Toggle expanded mode once and every subsequent result prints as a vertical list, one column per line\u2014ideal for tables with JSON columns or dozens of attributes.<\/p>\n Need the original layout back? Just run PostgreSQL\u2019s catalog is packed with built-in and user-defined functions. To inspect them quickly:<\/p>\n The plus sign ( Custom operators such as Alongside the symbol you\u2019ll see left and right argument types and the function that implements each operator\u2019s logic, giving you a full audit trail of non-standard behavior.<\/p>\n Inside one Variables persist until you close Need to check the date, tail a log, or clear the screen? Prefix any shell command with Because the database connection stays open, you can hop between SQL and shell utilities in a single workflow\u2014no extra terminal tab required.<\/p>\n Meta-commands don\u2019t change how SQL itself behaves, but they do<\/em> change how you experience it. By folding editor features, monitoring tricks, and OS access into one prompt, The six commands above are only a starting point. Type Next time you open the PostgreSQL CLI, keep one finger on the backslash. Your future self will thank you.<\/p>\n","protected":false},"excerpt":{"rendered":" If you manage PostgreSQL from a terminal you already know psql, the interactive client that ships with every installation. Most developers use it for the basics\u2014running SELECT statements, loading a .sql file, maybe poking around with \\dt to see which tables exist. Beneath that familiar surface, though, psql hides a rich toolbox of meta-commands. These commands, all prefixed with a backslash, live inside the client. They\u2019re not SQL, they\u2019re shortcuts built into psql itself, and they can make everyday tasks faster and far less error-prone.<\/p>\n","protected":false},"author":18,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[543],"tags":[546,240,550,547,544,549,548,545],"class_list":["post-1031","post","type-post","status-publish","format-standard","hentry","category-postgresql","tag-meta-commands","tag-postgresql","tag-postgresql-administration","tag-postgresql-cli","tag-psql","tag-psql-shortcuts","tag-sql-terminal","tag-sql-tips"],"yoast_head":"\npsql<\/code>, the interactive client that ships with every installation. Most developers use it for the basics\u2014running SELECT<\/code> statements, loading a .sql<\/code> file, maybe poking around with \\dt<\/code> to see which tables exist.<\/p>\npsql<\/code> hides a rich toolbox of meta-commands<\/em>. These commands, all prefixed with a backslash, live inside<\/strong> the client. They\u2019re not SQL, they\u2019re shortcuts built into psql<\/code> itself, and they can make everyday tasks faster and far less error-prone.<\/p>\n
\n1.
\\watch<\/code> \u2014 Re-run Any Query on a Timer<\/h3>\npsql<\/code> can refresh the same result set over and over.<\/p>\nSELECT count(*) AS pending_orders\nFROM orders\nWHERE status = 'pending';\n\\watch 5 -- refresh every 5 seconds<\/code><\/pre>\n\\watch<\/code> to a file with \\o \/path\/log.txt<\/code> first, then cancel with Ctrl-C<\/strong> when you\u2019ve captured enough samples.<\/p>\n
\n2.
\\x<\/code> \u2014 Expanded Display for Wide Rows<\/h3>\n\\x -- turn it on\nSELECT * FROM invoices WHERE id = 42;<\/code><\/pre>\n\\x<\/code> again to toggle off.<\/p>\n
\n3.
\\df+<\/code> \u2014 Explore Functions in Detail<\/h3>\n\\df+ *.* -- every function in every schema\n\\df+ my_schema.* -- everything in one schema\n\\df+ public.my_func -- one specific function<\/code><\/pre>\n+<\/code>) adds verbose columns: argument list, return type, language, volatility, even the function body for SQL and PL\/pgSQL routines. When you inherit an unfamiliar database, \\df+<\/code> is the fastest way to map its procedural landscape.<\/p>\n
\n4.
\\do<\/code> \u2014 List All Operators<\/h3>\n@><\/code>, <@<\/code>, or ||<\/code> can be pivotal to an application yet invisible in the schema browser. \\do<\/code> surfaces them all:<\/p>\n\\do -- show every operator the server knows\n\\do text.* -- only operators defined for the text data type<\/code><\/pre>\n
\n5. Session Variables with
\\set<\/code> and :name<\/code><\/h3>\npsql<\/code> session you can create lightweight variables and interpolate them into any SQL statement.<\/p>\n\\set myid 123\nSELECT * FROM users WHERE id = :myid;\n\n\\set country_code '''US'''\nSELECT * FROM sales WHERE country = :country_code;<\/code><\/pre>\npsql<\/code>, making them perfect for ad-hoc scripts where you might otherwise edit the same constant in multiple places.<\/p>\n
\n6. Shell Escapes (
\\!<\/code>) \u2014 Drop to the OS Without Leaving psql<\/code><\/h3>\n\\!<\/code>.<\/p>\n\\! date\n\\! clear\n\\! tail -n 20 \/var\/log\/postgresql\/postgresql-16-main.log<\/code><\/pre>\n
\nWhy Learn These Commands?<\/h2>\n
psql<\/code> becomes an interactive playground rather than a plain statement runner. Fewer context switches mean fewer typos, faster feedback, and a smoother cognitive flow.<\/p>\n\\?<\/code> in any psql<\/code> session and you\u2019ll get a full, scrollable list\u2014everything from \\e<\/code> (edit the current query in $EDITOR<\/code>) to \\pset csv<\/code> (output as comma-separated values). Spend a coffee break exploring, and chances are you\u2019ll uncover something that cuts a recurring task in half.<\/p>\n