Re: still gin index creation takes forever
От
Tom Lane
Тема
Re: still gin index creation takes forever
Дата
Msg-id
22361.1226458937@sss.pgh.pa.us
Ответ на
still gin index creation takes forever (Ivan Sergio Borgonovo)
Список
Дерево обсуждения
still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Ivan Sergio Borgonovo <mail@webthatworks.it>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Re: still gin index creation takes forever Tom Lane <tgl@sss.pgh.pa.us>
Re: still gin index creation takes forever Teodor Sigaev <teodor@sigaev.ru>
Postgres 8.2.x support on Windows 2008 "Raji Sridar (raji)" <raji@cisco.com>
Re: Postgres 8.2.x support on Windows 2008 Raymond O'Donnell <rod@iol.ie>
Re: Postgres 8.2.x support on Windows 2008 "Joshua D. Drake" <jd@commandprompt.com>
Re: Postgres 8.2.x support on Windows 2008 Scott Marlowe <scott.marlowe@gmail.com>
[Q] ODBC connect shows RELEASE / SAVEPOINT on selects "V S P" <toreason@fastmail.fm>
[Q] ODBC Decimal(19,6) "V S P" <toreason@fastmail.fm>
Re: Postgres 8.2.x support on Windows 2008 "Raji Sridar (raji)" <raji@cisco.com>
Re: Postgres 8.2.x support on Windows 2008 "Joshua D. Drake" <jd@commandprompt.com>
Re: Postgres 8.2.x support on Windows 2008 "Raji Sridar (raji)" <raji@cisco.com>
Re: Postgres 8.2.x support on Windows 2008 Magnus Hagander <magnus@hagander.net>
Re: Postgres 8.2.x support on Windows 2008 Tom Lane <tgl@sss.pgh.pa.us>
Re: Postgres 8.2.x support on Windows 2008 "Joshua D. Drake" <jd@commandprompt.com>
Re: Postgres 8.2.x support on Windows 2008 Craig Ringer <craig@postnewspapers.com.au>
Re: Postgres 8.2.x support on Windows 2008 Dave Page <dpage@pgadmin.org>
Re: Postgres 8.2.x support on Windows 2008 Magnus Hagander <magnus@hagander.net>
Re: Postgres 8.2.x support on Windows 2008 "Dann Corbit" <DCorbit@connx.com>
Re: Postgres 8.2.x support on Windows 2008 John R Pierce <pierce@hogranch.com>
Re: Postgres 8.2.x support on Windows 2008 Howard Cole <howardnews@selestial.com>
Re: Postgres 8.2.x support on Windows 2008 Scott Marlowe <scott.marlowe@gmail.com>
Ivan Sergio Borgonovo writes: > Any suggestion about how to track down the problem? What you are describing sounds rather like a use-of-uninitialized-memory problem, wherein the behavior depends on what happened to be in that memory previously. If so, using a debug/cassert-enabled build of Postgres might help to make the behavior more reproducible. (Of course, if the result is that it's reproducibly fast, this doesn't get us much closer to solving the problem :-(. But it seems worth trying.) regards, tom lane
В списке pgsql-general по дате отправления