| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Herouth Maoz <herouth(at)unicell(dot)co(dot)il> |
| Cc: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>, Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Slow update |
| Date: | 2009-01-23 01:47:59 |
| Message-ID: | dcc563d10901221747w3c8e2491m8590ab64f015fc7f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 21, 2009 at 9:36 AM, Herouth Maoz <herouth(at)unicell(dot)co(dot)il> wrote:
> I have a test machine - but the data in there is test data, and it's a
> slower machine. A testing environment is good for development, but can
> hardly be used to really simulate the production machine for performance.
>
What the other poster was referring to was a staging system. A
staging system has the same amount of data and type of servers, and is
necessary if you really want to performance test something before you
do it on production.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nick Withers | 2009-01-23 03:11:48 | Segmentation fault in backend/access/heap/pruneheap.c: heap_page_prune_opt() calling PageIsPrunable () with NULL page on FreeBSD / PowerPC |
| Previous Message | Clemens Schwaighofer | 2009-01-22 23:58:03 | Re: how to avoid that a postgres session eats up all the memory |