Re: [BUGS] problem creating index in 6,5,3

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [BUGS] problem creating index in 6,5,3
Дата
Msg-id 8703.945457153@sss.pgh.pa.us
обсуждение исходный текст
Ответ на problem creating index in 6,5,3  (Karl DeBisschop <kdebisschop@range.infoplease.com>)
Ответы Re: [BUGS] problem creating index in 6,5,3  (Karl DeBisschop <kdebisschop@range.infoplease.com>)
Re: [BUGS] problem creating index in 6,5,3  (Karl DeBisschop <kdebisschop@range.infoplease.com>)
Re: [BUGS] problem creating index in 6,5,3  (Karl DeBisschop <kdebisschop@range.infoplease.com>)
Список pgsql-bugs
Karl DeBisschop <kdebisschop@range.infoplease.com> writes:
> The problem manifests itself as

> webusers=> CREATE INDEX zdaily_id ON daily (id);
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally
>         before or while processing the request.

Is a corefile dumped in the database directory when this happens?
If so, can you get a backtrace from it with gdb?

> This did work for us using 6.5.1 compiled in house.  Our problems
> started with the 6.5.3 RPM.

Hmm.  We have been seeing some reports recently of other odd behavior
with the Linux RPMs (see the "ordering RH6.1" thread on pgsql-hackers).
Would you take the time to compile 6.5.3 from source and see if you
still see the same behavior?

If you do this, please compile the backend with full debug+assert
support, which is to say
  (a) add --enable-cassert to the configure command;
  (b) do   make COPT=-g all  instead of just make all.
That should make the gdb backtrace a lot more informative, if
a coredump happens...

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Karl DeBisschop
Дата:
Сообщение: problem creating index in 6,5,3
Следующее
От: Karl DeBisschop
Дата:
Сообщение: Re: [BUGS] problem creating index in 6,5,3