Re: ALTER TABLE lock strength reduction patch is unsafe
| От | Andres Freund |
|---|---|
| Тема | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Дата | |
| Msg-id | 20140304223901.GD27273@alap3.anarazel.de обсуждение |
| Ответ на | Re: ALTER TABLE lock strength reduction patch is unsafe (Josh Berkus <josh@agliodbs.com>) |
| Список | pgsql-hackers |
On 2014-03-04 14:29:31 -0800, Josh Berkus wrote: > On 03/04/2014 11:43 AM, Andres Freund wrote: > > On March 4, 2014 8:39:55 PM CET, Simon Riggs <simon@2ndQuadrant.com> wrote: > >> I was going to add an option to increase lock level, but I can't see > >> why you'd want it even. The dumps are consistent... > > > > Mvcc scans only guarantee that individual scans are consistent, not that separate scans are. Each individual scan takesa new snapshot if there's been ddl. > I thought that we were sharing the same snapshot, for parallel dump? That snapshot is about data, not the catalog. And no, we can't easily reuse one for the other, see elsewhere in this thread for some of the reasons. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: