| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Date: | 2014-03-03 15:43:46 |
| Message-ID: | CA+U5nM+f9Cyv4Ufs14ODO7jrT2vkEYhGRcwJANwLgebX49Cw+w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3 March 2014 15:19, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Feb 27, 2014 at 3:12 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> What I'm
> really concerned about is whether there are other things like the
> SnapshotNow issues that can cause stuff to halt and catch fire. I
> don't know whether there are or are not, but that's my concern.
Of course its a concern, I feel it also. But that's why we have beta
period to handle the unknowns.
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...
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-03-03 15:49:31 | Re: heapgetpage() and ->takenDuringRecovery |
| Previous Message | Euler Taveira | 2014-03-03 15:41:00 | Re: pg_dump reporing version of server & pg_dump as comments in the output |