Re: Small Bug in GetConflictingVirtualXIDs
| От | Andres Freund |
|---|---|
| Тема | Re: Small Bug in GetConflictingVirtualXIDs |
| Дата | |
| Msg-id | 200912211704.59321.af@cybertec.de обсуждение исходный текст |
| Ответ на | Re: Small Bug in GetConflictingVirtualXIDs (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
On Monday 21 December 2009 16:38:07 Tom Lane wrote: > Alvaro Herrera <alvherre@commandprompt.com> writes: > > Andres Freund wrote: > >> The logic behind this seems fine except in the case of dropping a > >> database. There you very well might have a open connection without an > >> open snapshot. > > Perhaps the simplest fix is to ensure that drop database gets a snapshot? > I confess to not having followed the thread closely, but why is DROP > DATABASE special in this regard? Wouldn't we soon find ourselves > needing every utility command to take a snapshot? Because most other "entities" are locked when you access them. So on the standby the AccessExlusive (generated on the master) will conflict with whatever lock you currently have on that entity (on the slave). There are no locks for an idle session though. Andres
В списке pgsql-hackers по дате отправления: