Re: Storing a dynahash for an entire connection or
От | Andrew Dunstan |
---|---|
Тема | Re: Storing a dynahash for an entire connection or |
Дата | |
Msg-id | 456B60E6.5010307@dunslane.net обсуждение исходный текст |
Ответ на | Re: Storing a dynahash for an entire connection or (Neil Conway <neilc@samurai.com>) |
Ответы |
Re: Storing a dynahash for an entire connection or
|
Список | pgsql-hackers |
Neil Conway wrote: > On Mon, 2006-11-27 at 20:11 +0000, Tom Dunstan wrote: > >> That's the obvious solution (or perhaps in CurTransactionContext), but >> when the function is called in a subsequent transaction, how does it >> determine that the static pointer was allocated from a context which has >> since vanished? >> > > If you're content with your allocations never being automatically > released for the duration of the session (which sounds like the behavior > Greg would like, I'm guessing), you can just allocate the hash table in > TopMemoryContext, in which case you wouldn't need to worry about the > context of allocation vanishing beneath your feet. > > Maybe I have misunderstood, but I don't see in this case how to determine that the cached data is still valid. cheers andrew
В списке pgsql-hackers по дате отправления: