Здравствуйте! Monday, June 23, 2014, 10:31:57 PM, you wrote:
NS> Denis, NS> On 06/21/2014 08:10 AM, Simonov Denis wrote: >> A long-running transaction READ READ_COMMITED will not keep the garbage? >> Maybe we should introduce a new key TPB, if you want to maintain >> compatibility. NS> Yes, for READ_ONLY + READ COMMITTED transactions you will now NS> inhibit GC if you keep a cursor open NS> for a long time. nice (sarcazm). So, dilemma is to enable your behavior, and get versions stall, or get versions not stalled by GS by usual RC Read? I think here that we need new isc_tpb constant. Because if not, we will "break" current transaction garbage collection behavior. I'm suspicious that this will break current cursor stability, because I'm doubt that anyone have related on this, but, anyway, mostly people that used RC read was thinking about GC will not stuck. -- С уважением, Dmitry Kuzmenko, www.ibase.ru, (495) 953-13-34 ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
