Re: what happens when concurrent index create

On Tue, Apr 3, 2012 at 9:50 PM, leo xu <leoxu8703(at)gmail(dot)com> wrote:

> i read documents,i find it that concurrent index create don't lock
> write.but
> need scan table twice.it explain is following as:
> It scans the table once to initially build the index, then makes a second
> pass to look for things added after the first pass.
>
> please explain 1. what happens when concurrent index create .tks.
> 2.how to trace a backend what do somethings internal.for
> example oracle 10046 trace.
>
>
It seems you are looking for a similar behavior of sql_trace in oracle. You
can try pgstatstatements contrib module.

http://www.postgresql.org/docs/9.1/static/pgstatstatements.html

---
Regards,
Raghavendra
EnterpriseDB Corporation
Blog: http://raghavt.blogspot.com/

> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/what-happens-when-concurrent-index-create-tp5615720p5615720.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>