Re: CSStorm occurred again by postgreSQL8.2

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: CSStorm occurred again by postgreSQL8.2
Дата
Msg-id 19738.1154956177@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: CSStorm occurred again by postgreSQL8.2  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Ответы Re: CSStorm occurred again by postgreSQL8.2
Список pgsql-hackers
ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp> writes:
> The invokers of SubTrans module are two SubTransGetTopmostTransaction()
> in HeapTupleSatisfiesSnapshot(). When I disabled the calls, CSStorm did
> not occur. SubTransGetTopmostTransaction returns the argument without
> change when we don't use SAVEPOINTs.

> If we optimize for non-subtransactions, we can avoid to lock SubTrans
> for check visiblities of tuples inserted by top transactions.

Only for top transactions still in progress, so I doubt that would
help much.

I'm wondering about doing something similar to what
TransactionIdIsInProgress does, ie, make use of the PGPROC lists
of live subtransactions.  Suppose that GetSnapshotData copies not
only top xids but live subxids into the snapshot, and adds a flag
indicating whether the subxids are complete (ie, none of the subxid
lists have overflowed).  Then if the flag is set, tqual.c doesn't
need to do SubTransGetTopmostTransaction() before searching the
list.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: andrew@dunslane.net
Дата:
Сообщение: Re: proposal for 8.3: Simultaneous assignment for
Следующее
От: stark
Дата:
Сообщение: Re: "Constraint exclusion" is not general enough