Hi,
I stumbled upon a situation where the planner comes with a bad query
plan, but I wanted to mention upfront that I'm using a dated PG version
and I already see an update which mentions about improving planner
performance. I just wanted to check if this issue is already resolved,
and if
Hi,
I've a postgres 9.1 database used for map generating ( tiles ).
The system has 24Go RAM and 5 processors.
I'm using geoserver to generate the tiles.
My data used 8486 MB = psql -d gis -c SELECT
pg_size_pretty(pg_database_size('gis'))
I've carefully indexes the table by the the_geom column.
hello Micha,
i think that noone can tell you much without more information about your
system. roughly i would say that you could change the following parameters:
shared_buffers = 1024MB - 6GB
work_mem = 256MB - 30-50 MB
effective_cache_size = 5120MB - 16GB (depends on whether its a dedicated db
On Fri, Oct 14, 2011 at 8:19 PM, Josh Berkus j...@agliodbs.com wrote:
Vishnu,
I am using PostgreSQL 8.4 in windows. I have created a database and
some tables on it. Also created a table space and some tables in it. My
application inserts data into these tables in every second. The
Robins Tharakan robins.thara...@comodo.com wrote:
I stumbled upon a situation where the planner comes with a bad
query plan, but I wanted to mention upfront that I'm using a dated
PG version and I already see an update which mentions about
improving planner performance. I just wanted to
On 10/17/2011 04:48 AM, Micka wrote:
Hi,
I've a postgres 9.1 database used for map generating ( tiles ).
The system has 24Go RAM and 5 processors.
I'm using geoserver to generate the tiles.
My data used 8486 MB = psql -d gis -c SELECT
pg_size_pretty(pg_database_size('gis'))
I've carefully
2011/10/17 Micka mickamus...@gmail.com:
Hi,
I've a postgres 9.1 database used for map generating ( tiles ).
The system has 24Go RAM and 5 processors.
I'm using geoserver to generate the tiles.
My data used 8486 MB = psql -d gis -c SELECT
pg_size_pretty(pg_database_size('gis'))
I've
Hi,
I'll try to answer in-line.
On 10/17/2011 09:32 PM, Kevin Grittner wrote:
First off, did you use pg_upgrade from an earlier major release? If
so, be sure you've dealt with this issue:
Although I joined recently, I doubt whether pg_upgrade was used here.
And this doesn't look like the
