| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Hot standby, running xacts, subtransactions |
| Date: | 2009-02-25 20:39:55 |
| Message-ID: | 49A5AC9B.3010903@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
When we take the snapshot of running transactions in the master, in
GetRunningTransactionData(), it only includes top-level xids and those
subxids that are in the subxid caches. Overflowed subxids are not
included. Isn't that a problem? When the standby initializes the
recovery procs using the running xacts information, pg_subtrans doesn't
isn't set for the overflowed xids, because that information is not
included in the WAL record. If you're lucky, the information is there
already, but we don't generally guarantee pg_subtrans to survive crash
or restart.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-02-25 20:45:18 | Re: Synchronous replication & Hot standby patches |
| Previous Message | Robert Haas | 2009-02-25 20:14:39 | Re: Synchronous replication & Hot standby patches |