| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bob Lunney <bob_lunney(at)yahoo(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Cache lookup failure for index during pg_dump |
| Date: | 2010-03-03 23:37:51 |
| Message-ID: | 201003032337.o23NbpH23410@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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 <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexender | 2010-03-04 07:31:45 | BUG #5361: KOI8U issue |
| Previous Message | Oleg Serov | 2010-03-03 19:11:12 | Re: Bug in triggers |