Re: [PERFORM] Fighting the planner >:-(

2013-02-01 Thread Casey Allen Shobe
nity.census_user set statistics 500; ^ On Fri, Feb 1, 2013 at 4:55 PM, Виктор Егоров wrote: > 2013/2/1 Casey Allen Shobe : > > Rowcounts are shown in the earlier paste link, but apparently I forgot to > > include the census table -

Re: [PERFORM] Fighting the planner >:-(

2013-02-01 Thread Casey Allen Shobe
owcounts are shown in the earlier paste link, but apparently I forgot to include the census table - hewitt_1_0_factors_precalc_new has 4,135,890 rows, and census_user has 1846439 rows. Statistics target is the default at 100. -- Casey Allen Shobe ca...@shobe.info

Re: [PERFORM] Fighting the planner >:-(

2013-02-01 Thread Casey Allen Shobe
http://explain.depesz.com/s/5ml -- Casey Allen Shobe ca...@shobe.info

Re: [PERFORM] Fighting the planner >:-(

2013-02-01 Thread Casey Allen Shobe
f you've got the RAM try doubling > it, then double it again. See what happens to your plan then. > 21861KB. I tried setting it to 192MB and re-preparing the same statement. Here's the explain execute: http://explain.depesz.com/s/pZ0, which looks identical as before. -- Casey Allen Shobe ca...@shobe.info

Re: [PERFORM] Fighting the planner >:-(

2013-02-01 Thread Casey Allen Shobe
in a prepare statements. The explain plans are from explain execute hewitt_test (...): http://pgsql.privatepaste.com/00c582c840 Here is the correct explain plan for this statement (still bad): http://explain.depesz.com/s/c46 On Fri, Feb 1, 2013 at 12:11 PM, Casey Allen Shobe wrote: > So wh

[PERFORM] Fighting the planner >:-(

2013-02-01 Thread Casey Allen Shobe
epaste.com/c66fd497c9 PostgreSQL version is 8.4, and most of our GUC's are default. Thanks in advance for any suggestions. -- Casey Allen Shobe ca...@shobe.info

[PERFORM] Using materialized views for commonly-queried subsets

2006-03-09 Thread Casey Allen Shobe
might be of use to anybody else in a similar situation, so I thought I'd post it here. http://community.seattleserver.com/viewtopic.php?t=11 Feel free to reproduce as you see fit. Cheers, -- Casey Allen Shobe | [EMAIL PROTECTED] | 206-381-2800 SeattleServer.com, Inc. |

Re: [PERFORM] Performance nightmare with dspam (urgent) (resolved)

2005-06-06 Thread Casey Allen Shobe
n option at all right now. I think the most cost-effective road forward is to add 2 more drives to each of the existing servers (which currently have 2 each). Cheers, -- Casey Allen Shobe | http://casey.shobe.info [EMAIL PROTECTED] | cell 425-443-4653 AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523 S

Re: [PERFORM] Performance nightmare with dspam (urgent) (resolved)

2005-06-06 Thread Casey Allen Shobe
On Wednesday 01 June 2005 20:19, Casey Allen Shobe wrote: > We've seen PostgreSQL performance as a dspam database be simply stellar on > some machines with absolutely no tuning to the postgres.conf, and no > statistics target altering. Wow. That took a phenomenally long time to pos

[PERFORM] Performance nightmare with dspam (urgent)

2005-06-05 Thread Casey Allen Shobe
7;m online on instant messengers (contact IDs shown below), monitoring my email, and will be on #postgresql on Freenode. Cheers, -- Casey Allen Shobe | http://casey.shobe.info [EMAIL PROTECTED] | cell 425-443-4653 AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523 SeattleServ

Re: [PERFORM] [dspam-users] Postgres vs. MySQL

2004-11-27 Thread Casey Allen Shobe
. To correct this behavior, adjust the query planner settings for the appropriate table/column with this command: alter table "dspam_token_data" alter "token" set statistics 200; analyze; Let me know if it help you. It worked wonders for me. -- Casey Allen Shobe [EMAI