Since few years, postgres began to impleent json and jsonb columns.

These columns could be very useful to implement pseudo organized information inside a database, for various reason: nestend optional fields could be a pain in the a** to implement in a rigorous sql vay (e.g. creating a foreign table vith optional data).

These optional fields usually needs to be convertend to and from json format to be produced and consumed by the frontned, so keeping them in json could also be performant.

Postgresql provides two different type of columns: json and jsonb, with different approach.

For example, a payload for a simple score page could be easily implemented with jsonb fields:

crate table:

create table score (
    id serial not null primary key,
    info jsonb not null
);

update or Insert key:

update score set info = info || '{"query": "last:4"}' 
where info->'name' = '"Marto"'::jsonb;

delete key:

update score set info = info -'query'
where info->'name' = '"Marto"'::jsonb;