Euler Taveira de Oliveira wrote: > Tom Lane escreveu: > > The window for this sort of thing isn't very large, because the first > > thing pg_dump does is acquire AccessShareLock on every table it intends > > to dump, and past that point it won't be possible for anyone to modify > > the table's DDL. But it can happen. > > > I did not see it documented anywhere. Should we at least add a comment at the > top of pg_dump documenting this behavior? Attached is a proposed patch using > your own words.
Applied, thanks. I also added the URL of the discussion. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
