Skip site navigation (1) Skip section navigation (2)

Hot standby, freezing

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Hot standby, freezing
Date: 2009-11-11 10:35:50
Message-ID: 4AFA9386.5040901@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers 
While reading through the patch for what must be the 100th time by now,
it occurred to me that this comment in heap_xlog_freeze:

+       /*
+        * Freezing tuples does not require conflict processing
+        */

is plain wrong. In the master, we can freeze the xmin of a tuple that's
not yet visible to all read-only transactions in the standby. We do need
conflict processing there.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

Responses

pgsql-hackers by date

Next:From: Albe LaurenzDate: 2009-11-11 11:15:26
Subject: Re: [HACKERS] PostgreSQL 8.3.8 on AIX5.3 : compilation failed
Previous:From: Heikki LinnakangasDate: 2009-11-11 08:03:33
Subject: Re: Hot Standby status

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group