Improved vacuum in PostgreSQL 13

Re:Improved vacuum in PostgreSQL 13 by PudgePacket on Tuesday May 12, 2020 @09:17AM (#23153624)

Maybe a silly question but what is the point of an insert-only table. Surely it must be read/used in some capacity ? Do they mean "insert heavy"?

[ Parent | on HN ]

Re:Improved vacuum in PostgreSQL 13 by brianwawok on Tuesday May 12, 2020 @09:19AM (#23153645)

Means not updated. Say Www visitor logs. No reason to ever update a previous log. What happened happened.

[ Parent | on HN ]

Re:Improved vacuum in PostgreSQL 13 by PudgePacket on Tuesday May 12, 2020 @10:45AM (#23154557)

[ Parent | on HN ]

Re:Improved vacuum in PostgreSQL 13 by CameronNemo on Tuesday May 12, 2020 @11:12AM (#23154836)

Selects would still work. But non insert DML would be disallowed I assume (delete, update).

[ Parent | on HN ]

Re:Improved vacuum in PostgreSQL 13 by blattimwind on Tuesday May 12, 2020 @09:20AM (#23153657)

Data is only inserted, not changed or deleted.

[ Parent | on HN ]

Re:Improved vacuum in PostgreSQL 13 by PudgePacket on Tuesday May 12, 2020 @10:46AM (#23154561)

[ Parent | on HN ]

Re:Improved vacuum in PostgreSQL 13 by 22c on Tuesday May 12, 2020 @10:51AM (#23154609)

You seem to be missing that data can still be read after it is insterted, provided it is not updated. So think if more like WORM rather than write-only.

[ Parent | on HN ]

Re:Improved vacuum in PostgreSQL 13 by sandGorgon on Tuesday May 12, 2020 @10:55AM (#23154649)

for compliance. you want this behavior to be enforced at the database level so that any buggy code does not edit a previous row.

[ Parent | on HN ]