Re: Recreating indices safely
От | Denis Perchine |
---|---|
Тема | Re: Recreating indices safely |
Дата | |
Msg-id | 200109202105.f8KL5mt02135@gw.ac-sw.com обсуждение исходный текст |
Ответ на | Re: Recreating indices safely (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-general |
On Wednesday 19 September 2001 11:25, Tom Lane wrote: > Denis Perchine <dyp@perchine.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@perchine.com HomePage: http://www.perchine.com/dyp/ FidoNet: 2:5000/120.5 ----------------------------------
В списке pgsql-general по дате отправления: