| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ToDo: no blocking (waiting) DDL |
| Date: | 2016-12-13 12:07:49 |
| Message-ID: | CAFj8pRCDWQELe3B01Onf5q1Yu2EaO7uwht6+G2yWfSHZLLx9Hg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2016-12-13 13:03 GMT+01:00 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:
> Pavel Stehule wrote:
> > Hi
> >
> > I don't remember well, there was maybe similar ToDo.
> >
> > Yesterday I got a incident on high load system when I executed DROP INDEX
> > cmd.
> >
> > This statement waited on a finish of long transaction, but it stopped any
> > other statements.
> >
> > Can be nice when waiting on lock statement doesn't block another
> > statements.
>
> https://postgr.es/m/CAKddOFDz0+F2uspVN5BZgtN7Wp+
> vQbeLuQPWfvGwap5JZvXPxQ(at)mail(dot)gmail(dot)com
yes, it is it. Can be applied on some DDL statements too.
Thank you
regards
Pavel
>
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | amul sul | 2016-12-13 12:53:35 | Re: pg_background contrib module proposal |
| Previous Message | Alvaro Herrera | 2016-12-13 12:03:37 | Re: ToDo: no blocking (waiting) DDL |