GSoC proposal for pgAdmin 4 bytea support - Mailing list pgsql-hackers

From Haoran Yu
Subject GSoC proposal for pgAdmin 4 bytea support
Date
Msg-id CAJNJMF_R5NHYnaG_+VgPF6vCr0znKOLn_p_H8wr3F0QJR_utRg@mail.gmail.com
Whole thread Raw
Responses Re: GSoC proposal for pgAdmin 4 bytea support
List pgsql-hackers
Dear PostgreSQL community,

I have submitted a proposal for the project pgAdmin 4 bytea support. The project discusses storing media content (images, audio, video) as bytea. However, I have a quick question. What does bytea data look like typically when storing media content? What I had in mind is, media contents that uses MIME type, which are rendered as part of HTML. For example, the following is rendered as a red dot:

'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAUA
AAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO
9TXL0Y4OHwAAAABJRU5ErkJggg==’

This string is decoded to bytea, and I stored it in a bytea column.

What are some other examples of using bytea to store media content, not necessarily using the MIME type? Is there a way to detect the type of these media (audio, image) stored in bytea?

Another question I had is, I read that there are performance-related issues for storing media in bytea. Are there practical ways to store bytea data that does not face performance-related issues? For example, storing large media content using multiple bytea parts, and reassembling them together once retrieved from the database?

Thank you,
Howard



pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Protect syscache from bloating with negative cache entries
Next
From: Yugo Nagata
Date:
Subject: Re: Implementing Incremental View Maintenance