| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DDL Damage Assessment |
| Date: | 2014-10-02 21:19:15 |
| Message-ID: | 20141002211915.GA5311@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Geoghegan wrote:
> Why is NOWAIT only supported for SET TABLESPACE? I guess it's just a
> particularly bad case. NOWAIT might be the wrong thing for DDL
> generally.
I didn't realize we supported NOWAIT for SET TABLESPACE. My hunch is
that if we have that, it should really be supported for anything that
does a table rewrite, or perhaps even anything that requires a full
table scan (such as adding a new CHECK constraint).
OTOH it does seem a wart to have NOWAIT in alter table generally. You
can get the same effect by doing a LOCK TABLE .. NOWAIT and then ALTER
TABLE, right?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-10-02 21:19:56 | Re: DDL Damage Assessment |
| Previous Message | Andres Freund | 2014-10-02 21:16:04 | Re: DDL Damage Assessment |