<br />The following sequence of commands causes server crash.<br /><br />postgres=# BEGIN TRANSACTION READ WRITE ;<br
/>BEGIN<br/>postgres=# SELECT * FROM pg_class FOR UPDATE;<br />FATAL: cannot assign TransactionIds during recovery<br
/>STATEMENT: SELECT * FROM pg_class FOR UPDATE;<br />FATAL: cannot assign TransactionIds during recovery<br />server
closedthe connection unexpectedly<br /> This probably means the server terminated abnormally<br /> before
orwhile processing the request.<br /> The connection to the server was lost. Attempting reset: Succeeded.<br /><br
/><br/>I think we should disallow starting a read-write transaction during recovery. The patch attempts to do that by
settingtransaction mode to read-only, but not enough to prevent somebody to explicitly mark the transaction as
read-write.<brclear="all" /><br />Thanks,<br />Pavan<br /><br />-- <br />Pavan Deolasee<br />EnterpriseDB <a
href="http://www.enterprisedb.com">http://www.enterprisedb.com</a><br/>
