Обсуждение: Storing session-local data
Hi guys. How can I store session-local data in an efficient way (I need to store every primary key/oid value for every changed row using triggers)?? I tried to use session-local temporary table, but it doesn't work with PREPARE TRANSACTION... Any ideas?
Elijah Epifanov wrote: > How can I store session-local data in an efficient way (I need to store > every primary key/oid value for every changed row using triggers)?? > I tried to use session-local temporary table, but it doesn't work with > PREPARE TRANSACTION... We might be able to relax that restriction so that you could use a "on commit delete rows" or "on commit drop" kind of temporary table in a global transaction. Would that help you? Maybe a silly queestion, but are you sure you need 2-phase commit? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
That would definitely help ))) 2) Question isn't silly)) I don't need it right now, but may (with high degree of probability) need it in future. Heikki Linnakangas wrote: > Elijah Epifanov wrote: >> How can I store session-local data in an efficient way (I need to store >> every primary key/oid value for every changed row using triggers)?? > >> I tried to use session-local temporary table, but it doesn't work with >> PREPARE TRANSACTION... > > We might be able to relax that restriction so that you could use a "on > commit delete rows" or "on commit drop" kind of temporary table in a > global transaction. Would that help you? > > Maybe a silly queestion, but are you sure you need 2-phase commit? >
Bruce, could you add this to the TODO, please? * Allow "on commit delete rows" and "on commit drop" kind of temporaray tables to be used in global transactions Elijah Epifanov wrote: > That would definitely help ))) > > 2) Question isn't silly)) I don't need it right now, but may (with high > degree of probability) need it in future. > > Heikki Linnakangas wrote: >> Elijah Epifanov wrote: >>> How can I store session-local data in an efficient way (I need to store >>> every primary key/oid value for every changed row using triggers)?? >> >>> I tried to use session-local temporary table, but it doesn't work with >>> PREPARE TRANSACTION... >> >> We might be able to relax that restriction so that you could use a "on >> commit delete rows" or "on commit drop" kind of temporary table in a >> global transaction. Would that help you? >> >> Maybe a silly queestion, but are you sure you need 2-phase commit? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com