Re: simultaneously reducing both memory usage and runtime for a query
От | Bruce Momjian |
---|---|
Тема | Re: simultaneously reducing both memory usage and runtime for a query |
Дата | |
Msg-id | 201003311933.o2VJXeh09398@momjian.us обсуждение исходный текст |
Ответ на | Re: simultaneously reducing both memory usage and runtime for a query (Faheem Mitha <faheem@email.unc.edu>) |
Ответы |
Re: simultaneously reducing both memory usage and runtime
for a query
|
Список | pgsql-general |
Faheem Mitha wrote: > > > On Sun, 28 Mar 2010, Tom Lane wrote: > > > Faheem Mitha <faheem@email.unc.edu> writes: > >> ... In any case, feedback would be helpful. Details of my attempts > >> at optimization are at > >> http://bulldog.duhs.duke.edu/~faheem/snppy/opt.pdf > > > > By and large, this is not the way to ask for help on the Postgres lists. > > If you're supplying extremely large test data or something, it's fair to > > provide a link instead of putting the information in-line, but otherwise > > you should try to make your email self-contained. Those of us who are > > willing to help are not here just to help you --- we'd like other people > > to learn from it too, both at the time and later from the archived > > discussion. So the information needs to be in the email thread, not > > only on some transient web page. > > I submitted a modified self-contained email as requested, but it does not > appear to have made it to the list, and I never got any kind of reject > message. It was around 1000 lines with no attachments. Is there a size > limit for posts, and if so, what is it? If it was rejected due to some > filter, it would be desirable (and polite) if the recepient was told what > happened. The bottom line is that this email list is best at answering short, detailed questions. Larger questions that require a lot of analysis by readers are often ignored. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com
В списке pgsql-general по дате отправления: