Re: what happens when concurrent index create

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "leo xu *EXTERN*" <leoxu8703(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: what happens when concurrent index create
Date: 2012-04-04 07:35:00
Message-ID: D960CB61B694CF459DCFB4B0128514C207B2C9CB@exadv11.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

leo xu 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.

You quoted the explanation above...
If you need to know more, read the source: it is the function
DefineIndex
in src/backend/commands/indexcmds.c

> 2.how to trace a backend what do somethings
internal.for
> example oracle 10046 trace.

SET log_min_messages=DEBUG5;

Then do what you want logged. Afterwards read the log file.

You need to be superuser for this command. If you want to switch
to a regular user after issuing the command, say

SET SESSION AUTHORIZATION some_user;

Yours,
Laurenz Albe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2012-04-04 07:47:40 Re: Unable to createlang
Previous Message Raghavendra 2012-04-04 03:24:35 Re: Unable to createlang