Tom Lane escribió: > Noah Misch <n...@leadboat.com> writes: > > A slight variation on the committed approach would be to add a "_scannable" > > relation fork. > > Not very transaction-safe, I think (consider crash midway through a > transaction that adds or removes the fork), and in any case orders of > magnitude more expensive than looking at a pg_class field. This really > needs to be catalog state, not filesystem state.
We could revive the pg_class_nt patch proposed a decade ago, perhaps ... -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
