[PERFORM] Slow query: table iteration (8.3)

Hitting a performance issues that I'm not sure how to diagnose. SELECT highscores_for_steps_and_card(s.id, 591, 1) FROM stomp_steps s; Seq Scan on stomp_steps s (cost=0.00..793.52 rows=2902 width=4) (actual time=26509.919..26509.919 rows=0 loops=1) Total runtime: 26509.972 ms The inner function

Re: [PERFORM] Constraint propagating for equal fields

2010/1/28 Віталій Тимчишин > > I've always thought that PostgreSQL would propagate constraint from field1 to > field2 if condition says field1=field2, but this does not seem the case: version? -- greg -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make change

Re: [PERFORM] Limited Shared Buffer Problem

Cédric Villemain wrote: AFAIK effective_cache_size is estimation of OS Page Cache + Estimated Cache in shared_buffers. Yes, the total value you set is used as is, and should include both pieces of memory. The planner doesn't add the shared_buffers value to the total first for you, as some

[PERFORM] Re: Faster CREATE DATABASE by delaying fsync (was 8.4.1 ubuntu karmic slow createdb)

On Tue, Jan 19, 2010 at 3:25 PM, Tom Lane wrote: > That function *seriously* needs documentation, in particular the fact > that it's a no-op on machines without the right kernel call.  The name > you've chosen is very bad for those semantics.  I'd pick something > else myself.  Maybe "pg_start_dat

Re: [PERFORM] Limited Shared Buffer Problem

Thanx, I will try out that recommendation. On Fri, Jan 29, 2010 at 11:53 AM, Richard Neill wrote: > > > **Rod MacNeil wrote: > >> Hi All, >> >> I have a server running CentOS5 with 6gb of memory that will run postgres >> 8.3 exclusively. >> I would like to allocate 4gb of the memory to shared b

Re: [PERFORM] Limited Shared Buffer Problem

2010/1/29 Richard Neill : > > > **Rod MacNeil wrote: >> >> Hi All, >> >> I have a server running CentOS5 with 6gb of memory that will run postgres >> 8.3 exclusively. >> I would like to allocate 4gb of the memory to shared buffers for postgres. > > It might be worth pausing at this point: > > The v

Re: [PERFORM] Limited Shared Buffer Problem

You are probably running 32bit OS. So the problem is that the OS cannot allocate more than 3G of memory continuous . Then the only solution is to migrate to a 64bit OS. 2010/1/29 **Rod MacNeil : > Hi All, > > I have a server running CentOS5 with 6gb of memory that will run postgres > 8.3 exclusive

Re: [PERFORM] Limited Shared Buffer Problem

Richard Neill escribió: **Rod MacNeil wrote: Hi All, I have a server running CentOS5 with 6gb of memory that will run postgres 8.3 exclusively. I would like to allocate 4gb of the memory to shared buffers for postgres. It might be worth pausing at this point: The various postgresql tunin

Re: [PERFORM] Limited Shared Buffer Problem

On Fri, Jan 29, 2010 at 9:37 AM, **Rod MacNeil wrote: > Hi All, > > I have a server running CentOS5 with 6gb of memory that will run postgres > 8.3 exclusively. > I would like to allocate 4gb of the memory to shared buffers for postgres. > I have modified some kernel settings as follows: > > shmal

Re: [PERFORM] Limited Shared Buffer Problem

**Rod MacNeil wrote: Hi All, I have a server running CentOS5 with 6gb of memory that will run postgres 8.3 exclusively. I would like to allocate 4gb of the memory to shared buffers for postgres. It might be worth pausing at this point: The various postgresql tuning guides usually suggest

[PERFORM] Limited Shared Buffer Problem

Hi All, I have a server running CentOS5 with 6gb of memory that will run postgres 8.3 exclusively. I would like to allocate 4gb of the memory to shared buffers for postgres. I have modified some kernel settings as follows: shmall 1048576 pages 4,294,967,296 bytes shmmax 4,294,967,295 bytes I c