Re: [HACKERS] [PATCH] Transaction traceability - txid_status(bigint)
От | Simon Riggs |
---|---|
Тема | Re: [HACKERS] [PATCH] Transaction traceability - txid_status(bigint) |
Дата | |
Msg-id | CANP8+jLYNHdgtqp2vJmAtkJc7RYebqFm1twGSLjkrrbV_L_9-A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] [PATCH] Transaction traceability - txid_status(bigint) (Craig Ringer <craig@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] [PATCH] Transaction traceability - txid_status(bigint)
|
Список | pgsql-hackers |
On 22 March 2017 at 03:35, Craig Ringer <craig@2ndquadrant.com> wrote: > On 22 March 2017 at 09:49, Craig Ringer <craig@2ndquadrant.com> wrote: > >>> Overall, though, I think that 0001 looks far better than any previous >>> iteration. It's simple. It looks safe. It seems unlikely to break >>> anything that works now. Woo hoo! >> >> Funny that this started with "hey, here's a simple, non-invasive >> function for looking up the status of an arbitrary xid". > > Changes made per discussion. This looks good to me also. Does what we need it to do. I was a little worried by possible performance of new lock, but its not intended to be run frequently, so its OK. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: