Excerpts from Boszormenyi Zoltan's message of vie jul 13 18:11:27 -0400 2012:
> Regarding the lock_timeout functionality: the patch can be reduced to > about half of its current size and it would be a lot less intrusive if the > LockAcquire() callers don't need to report the individual object types > and names or OIDs. Do you prefer the verbose ereport()s or a > generic one about "lock timeout triggered" in ProcSleep()? For what it's worth, I would appreciate it if you would post the lock timeout patch for the upcoming commitfest. This one is already almost a month long now. That way we can close this CF item soon and concentrate on the remaining patches. This one has received its fair share of committer attention already, ISTM. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
