Re: Timing events WIP v1

Поиск
Список
Период
Сортировка
От Greg Smith
Тема Re: Timing events WIP v1
Дата
Msg-id 50A5DA19.2070507@2ndQuadrant.com
обсуждение исходный текст
Ответ на Re: Timing events WIP v1  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-hackers
On 11/15/12 10:26 AM, Josh Berkus wrote:
>
>> Extending this to save the key/value set and most of the other data I
>> mentioned before is pretty straightforward.
>
> Why not use Hstore?  Seriously?

I just haven't done that part yet.  The fact that hstore is the likely 
way to do it is why I said it's straightforward, and haven't gotten 
stressed about not having that finished.  I wanted to try and shake out 
some feedback on hook location and how best to deal with memory context, 
both of which might impact this.  Extending the current hook setup I've 
got here to pass data via hstore would mean it needs to pull into core.  If there's a better approach for adding a hook
thatavoids that I'd be 
 
happy to adopt it, I just haven't thought of one.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com



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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: autovacuum truncate exclusive lock round two
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Proposal for Allow postgresql.conf values to be changed via SQL