Hello:
When I traced the source code of PG more deeply.
I can find the following:
VirtualTransactionId *
GetCurrentVirtualXIDs(TransactionId limitXmin, bool excludeXmin0,
bool allDbs, int excludeVacuum,
int *nvxids)
{
……
for (index =
Hello:
Sorry for disturbing again.
I traced source code of PG, and found that:
When the 「create index concurrently 」statement is called,The following
calling relationship is there:
PortalRunMulti--> PortalRunUtility-->Standard_ProcessUtility-->DefineIndex
Here I omit some code of DefineIndex f
Thanks Jeff
But What I can't understand is:
In My first test, the "create index concurrently" works well.
In My second test, the "create index concurrently" can not work.
The difference is only on ecpg's select statement :
One use host variable of char (its value is of integer 14) in select
sta
On Thu, Jun 20, 2013 at 1:27 AM, 高健 wrote:
> Hello:
>
>
>
> I have question about PG's "create index concurrently". I think it is a
> bug perhaps.
>
>
>
> I make two tables tab01 and tab02, they have no relationships.
>
> I think "create index concurrently " on tab02 will not be influenced by
>
Hello:
I have question about PG's "create index concurrently". I think it is a
bug perhaps.
I make two tables tab01 and tab02, they have no relationships.
I think "create index concurrently " on tab02 will not be influenced by
transaction on tab01.
But the result differs:
My first prog
