Hans-Juergen Schoenig <[EMAIL PROTECTED]> writes: > Doing this for XIDs is pretty useless this days. > It is only targeted for command ids which are consumed heavily by > stored procedure languages. > It happens once on a while that a complex business logic procedure > runs out of command ids inside a transaction. > the idea is to give users a chance to avoid that. > touching XIDs does not make sense to me at all.
In view of the fact that 8.3 greatly reduced the CommandID consumption of typical plpgsql code http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php I wonder whether the case for wider CIDs hasn't likewise taken a major hit. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
