| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bug? Concurrent COMMENT ON and DROP object |
| Date: | 2010-07-08 00:29:43 |
| Message-ID: | 11530.1278548983@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Jul 6, 2010 at 10:59 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
>> Excerpts from Robert Haas's message of mar jul 06 22:31:40 -0400 2010:
>>> Hmm... so, maybe ShareUpdateExclusiveLock?
>>
>> So COMMENT ON will conflict with (auto)vacuum? Seems a bit weird ...
> Well, I'm open to suggestions... I doubt we want to create a new lock
> level just for this.
[ shrug... ] COMMENT ON is DDL, and most forms of DDL will conflict
with vacuum. I can't get excited about that complaint.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2010-07-08 00:32:12 | Re: Re: [COMMITTERS] pgsql: Fix log_temp_files docs and comments to say bytes not kilobytes. |
| Previous Message | Tom Lane | 2010-07-07 23:43:44 | Re: pg_dump and join aliases (was Re: [BUGS] ERROR: cannot handle unplanned sub-select) |