| From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-02-20 01:50:35 |
| Message-ID: | 4B7F3FEB.3070700@timbira.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
--
Euler Taveira de Oliveira
http://www.timbira.com/
| Attachment | Content-Type | Size |
|---|---|---|
| cmt.diff | text/x-patch | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-02-20 04:13:43 | Re: BUG #5015: MySQL migration wizard does not start |
| Previous Message | Tom Lane | 2010-02-20 00:39:51 | Re: Cache lookup failure for index during pg_dump |