Re: 64-bit CommandIds
От | Hans-Juergen Schoenig |
---|---|
Тема | Re: 64-bit CommandIds |
Дата | |
Msg-id | 48121CED.3090707@cybertec.at обсуждение исходный текст |
Ответ на | Re: 64-bit CommandIds (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-patches |
Tom Lane wrote: > Hans-Juergen Schoenig <hs@cybertec.at> writes: > >> Alvaro Herrera wrote: >> >>> Question for Hans-Juergen and Zoltan: have you tested 8.3 and do you >>> still see the need for this? >>> > > >> i have seen this problem two or three times within the past 2-3 years or >> so. so, it can basically happen in the field for some special purpose >> applications but i don't see this as an every day problem. it would be >> nice to have it in. >> > > So these experiences were pre-8.3, right? > > The reason that I'm harping on that is that plpgsql does a > CommandCounterIncrement for each expression it evaluates, whether > or not there's any visible database access. As of 8.3 that won't > cause consumption of CIDs, but before it did. I suspect that in a > lot of real-world scenarios, CID consumption from triggers will be > down by an order of magnitude. > > regards, tom lane > we found those problems when we dealt with stored procedures basically (during huge analysis and data modification transactions - rollup and materialize stuff, basically). i would think as well that it should have improved a lot. i have not tested with 8.3, however. on 8.2 it took something like 18 hours to reach that threshold - just to give you an impression. many thanks, hans -- Cybertec Schönig & Schönig GmbH PostgreSQL Solutions and Support Gröhrmühlgasse 26, A-2700 Wiener Neustadt Tel: +43/1/205 10 35 / 340 www.postgresql-support.de, www.postgresql-support.com
В списке pgsql-patches по дате отправления: