Copy or download query results in the Postgres data console
niv246
PROOP

18 hours ago

The Data tab's query editor renders results as a table I can only look at.

There's no way to copy the result set, no way to download it, and no way to copy

a single cell. The Logs view already has copy and download — the query results

just never got the same treatment.

My use case: I run read-only diagnostic SQL against my production Postgres

several times a day — counts with control columns, sanity checks on a

production incident — and I need to get the output somewhere else: into a chat

with an AI assistant that's helping me debug, into an issue, into a message to a

colleague. Today the only way is screenshots.

Why screenshots are painful here specifically:

  1. A result with more than ~5 columns scrolls horizontally, so one row needs two

    or three screenshots stitched together.

  2. Results paginate. A 17-row result came back as "Page 1 of 4" — four

    screenshots for something I could have copied in one keystroke.

  3. Long cell values open in a modal, which is another screenshot.

  4. Screenshots aren't text. Nobody downstream can grep them, diff them, or paste

    them into another query. If someone needs to re-run my check they have to

    retype the numbers by hand, which is exactly where transcription errors come

    from — and these are financial figures.

What I'd love to see:

  • A "Copy" button on the results panel, ideally with a format choice:

    CSV / TSV (pastes straight into a spreadsheet), JSON, and Markdown table

    (pastes straight into GitHub, Slack, or a chat).

  • A "Download .csv" button for larger result sets.

  • Copy a single cell, and copy a selected range of rows.

  • Copy the full result set, not just the current page — the pagination is a

    display concern, and having to page through it to copy it defeats the point.

Current workaround: screenshots, or rewriting the query as

select string_agg(...) so the whole answer collapses into one cell I can read

in a modal — which is me contorting the SQL to work around the UI.

Logs already do this well. The same affordance on query results would make the

data console genuinely usable for diagnostics instead of read-only.

Under Review

0 Threads mention this feature

0 Replies

Welcome!

Sign in to your Railway account to join the conversation.

Loading...