Close all connections from a Postgres database

100%

Close all connections from a Postgres database

✓ Published0🌍 Public

Last edited Dec 6, 2018

Created on Dec 6, 2018

This example shows how to forcibly terminate every active connection to a named Postgres database except the current session. The SQL query selects all rows from `pg_stat_activity` and calls `pg_terminate_backend(pid)` for each matching process ID, filtering by `datname = 'database'` and excluding the backend’s own PID. The query returns the full activity listing alongside the termination result for each row. The visualization relies solely on the Postgres system catalog function, with no external charting libraries or rendering pipeline.

AI-generated description

Similar vizzes

Loading thumbnail…

Connexion à PostgreSQL + histogramme avec ggplot2

This example demonstrates how to create a histogram directly from a PostgreSQL database table using R. The code first establishes a database connection with the `DBI` and `RPostgreSQL` packages, then uses `dplyr` and `dbplyr` to query the table as a remote data frame. The `ggplot2` library renders the histogram via `geom_histogram`, mapping a specified column to the aesthetic. Finally, the connection is explicitly closed with `dbDisconnect`. The code illustrates a workflow for plotting distributed data without loading it entirely into local memory.

RRCura

49% match

Loading thumbnail…

List schema and tables from all databases in PostgreSQL cluster

This example shows a two-step pipeline that first lists every database in a PostgreSQL cluster and then aggregates all user-defined schemas and tables from each database into a single CSV file. The first `psql` query retrieves database names, excluding `template0`, and writes them to `databases.txt`. A shell loop then runs a second `psql` query against each database, selecting `schemaname` and `tablename` while filtering out system schemas, and appends results with the database name to `all_tables.txt`. The code uses the PostgreSQL command-line client with `-t --csv` flags to output tab-separated CSV data.

TThomasG77

48% match

Loading thumbnail…

PostgreSQL command line cheatsheet

This example presents a text-based cheat sheet for PostgreSQL command-line tools, rendering a curated list of psql commands, configuration snippets, and handy SQL queries in a plain markdown document. It shows the core syntax for database management tasks, such as connecting to databases, listing tables and views, managing user roles, and adjusting server logging verbosity, alongside query examples for inspecting indexes, active sessions, and table sizes. The visualization relies on static code blocks and inline formatting, with no interactive graphics or JavaScript libraries; instead, it leverages the raw text content from a gist, emphasizing practical API references like `psql` meta-commands and `pg_stat_activity` queries.

AAngieLiang

48% match

Loading thumbnail…

Kill all tmux sessions and screen sessions.

This example shows how to terminate all active tmux and screen sessions via shell commands. It first lists tmux sessions, extracts session IDs by filtering lines containing colons, trimming with `cut`, and stripping trailing characters using `awk` and `substr`, then pipes them to `xargs kill`. For screen, it filters lines containing "Detached", parses the session identifier with `cut` and `awk`, and kills those processes similarly. The code relies on standard Unix utilities including `tmux`, `screen`, `grep`, `cut`, `awk`, `xargs`, and `kill`.

PP7h

48% match

Loading thumbnail…

PostgreSQL installation tutorial

This example presents a step-by-step guide for installing PostgreSQL across macOS, Linux, and Windows. It shows the terminal command `psql -U postgres` as the target for verifying a successful setup, then details OS-specific actions, such as using the Postgres.app on macOS, compiling from source via `wget` on Linux, and using the EnterpriseDB installer on Windows. The tutorial also covers checking the `$PATH` variable and verifying the server port with `lsof`.

115Dkatz

47% match

Loading thumbnail…

#localhost

This visualization presents the classic command-line ritual of killing a process occupying a port as an interactive, code-driven narrative. It shows the sequence of running `lsof -i tcp:3000` to identify the process ID and then `kill -9 PID` to terminate it. The code uses the `d3.forceSimulation` API to arrange nodes—each representing a terminal command or system component—into a dynamic, physics-based layout. The rendering relies on the D3.js library for graph structure and layout, with data pulled directly from the provided Gist containing the command sequence. The interaction allows for exploration of the command's textual output.

GGugaGongadze

45% match

Loading thumbnail…

Gist 0c701eddfaa4b93ee172

Two terminal sessions show failed attempts to import OpenStreetMap data into a PostgreSQL database using Osmosis, a Java command-line tool. The visualization captures log output from sequential runs of the `osmosis` command, displaying errors from Java's `java.net.ConnectException` when the database connection is refused. The first attempt fails because the `--truncate-pgsql` task receives an unexpected `port` argument, while the second fails because PostgreSQL is not running. The display highlights the pipeline's reliance on database configuration and connection handling, rendered as plain terminal text.

CCaged

43% match

Loading thumbnail…

Gist 61afda568887fcc603e1f9ef963925ec

This example demonstrates a QGIS Processing model that exports spatial data to a PostgreSQL/PostGIS database. The model chains two algorithms: `qgis:postgisexecuteandloadsql` to run SQL and load the result, followed by `qgis:importintopostgis` to write the output to a table named "out2" in the public schema. It uses the PostgreSQL connection "EPSG demo," sets UTF-8 encoding, and creates a geometry column. The model shows a reusable workflow for automating database ingestion directly from the QGIS Processing framework.

TThomasG77

41% match