Re: server crash in very big transaction [postgresql 8.0beta1] - Mailing list pgsql-bugs

From Tom Lane
Subject Re: server crash in very big transaction [postgresql 8.0beta1]
Date
Msg-id 11248.1093487142@sss.pgh.pa.us
Whole thread Raw
In response to Re: server crash in very big transaction [postgresql 8.0beta1]  ("ÿffffceÿffffac" "ÿffffbdÿffffaa" <jiangwei_1976@yahoo.com.cn>)
Responses Re: server crash in very big transaction [postgresql 8.0beta1]  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-bugs
"ÿffffceÿffffac" "ÿffffbdÿffffaa" <jiangwei_1976@yahoo.com.cn> writes:
> --- Alvaro Herrera <alvherre@dcc.uchile.cl> wrote:
>> Huh, so what kind of operations did you execute
>> within the transaction?

> There are 1600 tables in database 'db1', I wrote a
> pl/pgsql function "update_tables" like

> "
> FOR table IN SELECT relname FROM pg_class
> LOOP
>     ...
>     DROP INDEX ON ... ;
>     ALTER TABLE DROP CONSTRAINT ...;
>     ...
>     CREATE INDEX xxx ON TABLE xxx;
>     ...
>     ALTER TABLE xxx ADD PRIMARY KEY...
>     ALTER TABLE xxx ADD ...
>     ...
> END LOOP

Okay, so it was the number-of-deleted-files issue and not the
number-of-subtransactions issue.  Still says we have to allow
commit records to be bigger than 64K ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: BUG #1231: Probelm with transactions in stored code.
Next
From: Tom Lane
Date:
Subject: Re: BUG #1231: Probelm with transactions in stored code.