tiyukeji@126.com writes:
> canceling sql :
> CREATE INDEX CONCURRENTLY t_1_index
> ON t_1 USING btree
> (name);
> result:
> index t_1_index existï¼ but size 0
This is expected when using CREATE INDEX CONCURRENTLY. See the
notes at
http://www.postgresql.org/docs/9.3/static/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY
which say
"If a problem arises while scanning the table ... the CREATE INDEX command
will fail but leave behind an "invalid" index."
regards, tom lane