>From: smiley2211
>Subject: Re: [PERFORM] Upgraded from 7.4 to 8.1.4 QUERIES NOW SLOW!!!
>
>-> Seq Scan on encounters_questions_answers eqa
>(cost=1.00..17608.66 rows=464766 width=8) (actual
>time=0.003..735.934 row
RFORM] Upgraded from 7.4 to 8.1.4 QUERIES NOW SLOW!!!
Dennis,
Thanks for your reply.
No, the OLD server are no longer available (decommissioned) - the new
servers are definitely better h\w.
I do not have any queries to EXPLAIN ANALYZE as they are built by the
application and I am not allowed to e
In response to smiley2211 <[EMAIL PROTECTED]>:
>
> Dennis,
>
> Thanks for your reply.
>
> No, the OLD server are no longer available (decommissioned) - the new
> servers are definitely better h\w.
Says who? I've heard that one before, and I've seen it be false.
Some wonk replaced a 1Ghz system
Dennis,
Thanks for your reply.
No, the OLD server are no longer available (decommissioned) - the new
servers are definitely better h\w.
I do not have any queries to EXPLAIN ANALYZE as they are built by the
application and I am not allowed to enable logging on for that server - so
where do I go
> Old servers that housed 7.4 performed better than 8.1.4 version...are
> there any MAJOR performance hits with this version???
>
> I set the postgresql.conf setting to equal that of 7.4 and queries still
> run
> SLOW on 8.1.4...
We need to find a specific query that is slow now that was fast befo
Here are the requested lines...
There were 0 unused item pointers.
0 pages are entirely empty.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO: free space map contains 786 pages in 297 relations
DETAIL: A total of 5408 page slots are in use (including overhead).
5408 page slots are required to track
On 9/20/07, smiley2211 <[EMAIL PROTECTED]> wrote:
>
> How do I know if there is BLOATING??? I just ran vacuum verbose;
>
> Yes, autovacuum is on.
Post the last 4 or 5 lines from vacuum verbose.
---(end of broadcast)---
TIP 6: explain analyze is your
How do I know if there is BLOATING??? I just ran vacuum verbose;
Yes, autovacuum is on.
Thanks...Michelle
--
View this message in context:
http://www.nabble.com/Upgraded-from-7.4-to-8.1.4-QUERIES-NOW-SLOW%21%21%21-tf4489502.html#a12807959
Sent from the PostgreSQL - performance mailing list a
On 9/20/07, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> effort is going. I'm guessing you'll see a lot of id in there.
sorry, meant wa (wait)
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.
On 9/20/07, smiley2211 <[EMAIL PROTECTED]> wrote:
>
> No, I didn't UPGRADE it but that's what I inherited :( ...not sure of the
> code page stuff because I am not the one who did the upgrade...I'm not sure
> I know ENOUGH about POSTGRESQL to mess around with the codepage...
>
> Yes, I use vacuum an
No, I didn't UPGRADE it but that's what I inherited :( ...not sure of the
code page stuff because I am not the one who did the upgrade...I'm not sure
I know ENOUGH about POSTGRESQL to mess around with the codepage...
Yes, I use vacuum analyze...
Yes, I used the postgresql.conf of 7.4 and tried t
smiley2211 wrote:
Hello all,
Old servers that housed 7.4 performed better than 8.1.4 version...are there
any MAJOR performance hits with this version???
Are you using the default UNICODE encoding for your databases??
This could potentially translate into a performance hit (considerable?
Ma
Hello all,
Old servers that housed 7.4 performed better than 8.1.4 version...are there
any MAJOR performance hits with this version???
I set the postgresql.conf setting to equal that of 7.4 and queries still run
SLOW on 8.1.4...
I have perform maintenance tonight on the 8.1.4 server - any ideas
13 matches
Mail list logo
