jakob / jakob/Postico

Bytea data type slows down postico

Open
#57 3 comments 2 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
485
Forks
8
PR merge metrics
No merged PRs in 30d

Description

We have a table with a bytea column to store big images (about 44 MB per image). Now every time I retrieve data form this table with postico (f.g. clicking on the table name), the application hangs till the 44 MB per row is loaded from the database.

![capturfiles_67](https://cloud.githubusercontent.com/assets/5220162/9519424/e5a47842-4cbe-11e5-95ac-cac3f1bed231.png)

It would be great to have an option to disable bytea loading and only load it if the user is requesting it.

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the hang with a PostgreSQL table containing 44 MB bytea rows and inspect the table-browsing retrieval path; the issue names no source file or test. Done means browsing the table no longer loads bytea values until explicitly requested, while other columns remain available.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql
Domain
database
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.