<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<div>Is it possible to implement a "read your own writes" pattern with pgpool?</div>
<div>Specifically, some of the application transactions update some data and then as a last step read all of the updated data back.</div>
<div>I know this is not necessarily a best practice but this is how the app currently works.</div>
<div>With pgpool the writes would go to the primary and the final read would go to the standby which would not yet have the uncommitted writes.</div>
<div>Is there a way to enforce this stickiness so that all statements belonging to the same transaction would go to the same node</div>
<div>which in this case would be the primary?</div>
<div>I cannot update the application to include any "hints" in the statements.</div>
<div><br>
</div>
</div>
</body>
</html>