Re: Recreating indices safely

From: Denis Perchine <dyp(at)perchine(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Recreating indices safely
Date: 2001-09-20 21:08:19
Message-ID: 200109202105.f8KL5mt02135@gw.ac-sw.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday 19 September 2001 11:25, Tom Lane wrote:
> Denis Perchine <dyp(at)perchine(dot)com> writes:
> > BTW, using begin; lock table; create index;drop index;commit; is not
> > working,
>
> ??
>
> regression=# create table foo (f1 text);
> CREATE
> regression=# create index fooi1 on foo(f1);
> CREATE
> regression=# begin;
> BEGIN
> regression=# lock table foo;
> LOCK TABLE
> regression=# create index fooi2 on foo(f1);
> CREATE
> regression=# drop index fooi1;
> DROP
> regression=# end;
> COMMIT
>
> Please define "not working".

Hmmm... I got deadlock detected... Something was interfered as well...

BTW, also sometimes I get the following message which really intrigues me.

ERROR: Index 8734149 does not exist

When I restart my application it just disappears... Is it possible, that backends loose
information about updated indices? And how can I debug/detect this?

--
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp(at)perchine(dot)com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alex K. 2001-09-20 22:18:46 what is wrong with this SQL?
Previous Message Mihai Gheorghiu 2001-09-20 20:58:04 Global constants