Hi -hackers. >From time to time pg_largeobject comes up as an issue with being implemented as a system-catalog. As I see it, there are 2 relevant use-cases for improving the situation: 1. Being able to pg_dump *without* any LOs (think of it as without the contents of pg_largeobject). This is very handy for testing/troubleshooting. 2. Being able to move pg_largeobject to a different tablespace *without* turning on system_table_mods. This is important for people storing LOTS of large-objects on separate disks (non-SSD) and hence in a different tablespace.
Anyone willing to discuss this? Thanks. -- Andreas Joseph Krogh CTO / Partner - Visena AS Mobile: +47 909 56 963 andr...@visena.com <mailto:andr...@visena.com> www.visena.com <https://www.visena.com> <https://www.visena.com>