| |||||||||||||
How 3.6 nearly broke PostgreSQLHow 3.6 nearly broke PostgreSQLPosted Oct 3, 2012 19:00 UTC (Wed) by corbet (editor, #1)In reply to: How 3.6 nearly broke PostgreSQL by jberkus Parent article: How 3.6 nearly broke PostgreSQL FWIW, the discussion in kernelland was based on the assumption that this regression was the kernel's problem. Nobody there suggested telling the PostgreSQL developers to come up with a new locking scheme.
(Log in to post comments)
|
|||||||||||||