Hello, >I was more dreaming of something like "disable read write locks or >mutexes" when accessing the database in read-only mode, but sadly this >case seems unhandled.
You could use transactions in read only mode. They do not generate XID's,which reduces the need to do VACUUM to protect against XID wraparound. Ref: http://postgresql.nabble.com/read-only-transactions-td3209290.html -- View this message in context: http://postgresql.nabble.com/Optimizing-a-read-only-database-tp5849746p5850107.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
