Tom Lane wrote: > "Heikki Linnakangas" <[email protected]> writes: > > The trivial fix is to not call CacheInvalidateRelcache() in recovery > > (patch attached). Another option is to put the check into > > CacheInvalidateRelcache() itself, but in the name of consistency we > > should then put the same check into the other CacheInvalidate* variants > > as well. As nbtinsert.c is the only place that calls > > CacheInvalidateRelcache during WAL replay, I'm going to do the trivial fix. > > This will need to be revisited if we ever hope to get read-only slaves > working. But I agree with the trivial fix for now (especially in the > back branches).
Is this being handled by the hot standby patch? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
