Re: pg_dump potential bug
От | Marcin Kowalski |
---|---|
Тема | Re: pg_dump potential bug |
Дата | |
Msg-id | 99uqrf$cmv$1@news.tht.net обсуждение исходный текст |
Ответ на | Re: pg_dump potential bug (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-admin |
Hi Thanks for the help, in fact that is Exactly what is wrong. The pg_shadow table has duplicated entries in it, I think I'm going to create a unique index on it. BTW I've migrated the entrie database to PG7.1RC1, running quite a big search on the database basically involving a huge amount of selects. Currently I'm curising at 1250 selects per second (simple select, no Joins) from multiple tables with mutliple data, pretty fast I think. (But I still have +- 10 Million to do :-) ). ANyone have any ideas on how to improve performace, currently have indices on key fields and am clustering (vacuum + vacuum analyze done)?? Are there any command line parameters I can try to increase performance..?? Thanks in ADvance MarCIn Tom Lane wrote: > Marcin Kowalski <kowalski@datrix.co.za> writes: >> Is it possible that one of the system tables has been corrupted and shows >> multiple entries for the tables? > > Come to think of it, this is a fairly likely behavior if you have > multiple entries in pg_shadow with the same usesysid. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://www.postgresql.org/search.mpl >
В списке pgsql-admin по дате отправления: