On Mon, Feb 28, 2011 at 6:38 PM, Robert Haas robertmh...@gmail.com wrote:
Remember that it's not only about saving shared memory, it's also
about making sure that the snapshot reflects a state of the database
that has actually existed at some point in the past. Furthermore, we
can easily
Marko Tiikkaja marko.tiikk...@cs.helsinki.fi writes:
On 2011-02-28 9:36 PM, Tom Lane wrote:
OK, so the intent is that in all cases, we just advance CID and don't
take a new snapshot between queries that were generated (by rule
expansion) from a single original parsetree? But we still take a
On Tue, Mar 1, 2011 at 9:19 AM, Simon Riggs si...@2ndquadrant.com wrote:
On Mon, 2011-02-28 at 18:40 +, Simon Riggs wrote:
SyncRepReleaseWaiters should be called when walsender exits. Otherwise,
if the standby crashes while a transaction is waiting for replication,
it waits infinitely.
Thanks for update of the patch!
On Tue, Mar 1, 2011 at 3:40 AM, Simon Riggs si...@2ndquadrant.com wrote:
SyncRepRemoveFromQueue seems not to be as short-term as we can
use the spinlock. Instead, LW lock should be used there.
You seem to have forgotten to fix the above-mentioned issue.
A
On Tue, Mar 1, 2011 at 3:39 AM, Simon Riggs si...@2ndquadrant.com wrote:
PREPARE TRANSACTION and ROLLBACK PREPARED should wait for
replication as well as COMMIT PREPARED?
PREPARE - Yes
ROLLBACK - No
Further discussion welcome
If we don't make ROLLBACK PREPARED wait for replication, we
On Tue, 2011-03-01 at 15:25 +0900, Fujii Masao wrote:
On Tue, Mar 1, 2011 at 9:19 AM, Simon Riggs si...@2ndquadrant.com wrote:
On Mon, 2011-02-28 at 18:40 +, Simon Riggs wrote:
SyncRepReleaseWaiters should be called when walsender exits. Otherwise,
if the standby crashes while a
101 - 106 of 106 matches
Mail list logo
