| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: deadlock_timeout at < PGC_SIGHUP? |
| Date: | 2011-03-29 14:23:27 |
| Message-ID: | 1301408551-sup-7970@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Greg Stark's message of mar mar 29 11:15:50 -0300 2011:
> Alternatively we could have the deadlock timer reset all the time and
> fire repeatedly. Then we could just have all backends ignore the
> deadlock if they're not the lowest priority session in the cycle. But
> this depends on everyone knowing everyone else's priority (and having
> a consistent view of it).
Presumably it'd be published in MyProc before going to sleep, so it'd be
available for everyone and always consistent. Not sure if this requires
extra locking, though.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-03-29 14:26:21 | Re: Another swing at JSON |
| Previous Message | Greg Stark | 2011-03-29 14:15:50 | Re: deadlock_timeout at < PGC_SIGHUP? |