| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Date: | 2014-03-03 18:58:46 |
| Message-ID: | 20140303185846.GB3476935@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 03, 2014 at 03:43:46PM +0000, Simon Riggs wrote:
> The question is are there any specific areas of concern here? If not,
> then we commit because we've done a lot of work on it and at the
> moment the balance is high benefit to users against a non-specific
> feeling of risk.
>
> @Noah - Last call...
I am not specifically aware of any outstanding problems. I have planned to
give this a close look, but it will be at least two weeks before I dig out far
enough to do so. If that makes it a post-commit review, so be it.
--
Noah Misch
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-03-03 19:03:06 | Re: [PATCH] Use MAP_HUGETLB where supported (v3) |
| Previous Message | Noah Misch | 2014-03-03 18:57:36 | Re: ALTER TABLE lock strength reduction patch is unsafe |