Scott Marlowe wrote:
> While I don't wholly disagree with periodic reindexing, I do recommend
> that one keeps track of bloat. It's easy enough to have an alarm that
> goes off if any index gets over 50% dead space, then go look at the
> database.
Reading this list, I've noticed that:
- Many ad
On Tue, Jan 6, 2009 at 9:05 AM, Grzegorz Jaśkiewicz wrote:
> you don't have to reindex too often - it locks exclusively whole
> table, just like vacuum full. Just do it every few months, depending
> on db growth.
While I don't wholly disagree with periodic reindexing, I do recommend
that one keep
t: Tuesday, January 06, 2009 12:02 PM
To: Scot Kreienkamp
Cc: pgsql-general@postgresql.org; Scott Marlowe
Subject: Re: [GENERAL] Vacuum problems
- "Scot Kreienkamp" wrote:
> Thanks for the advice Scott. I've taken out the vacuum fulls
> entirely.
> I've now got a ni
- "Scot Kreienkamp" wrote:
> Thanks for the advice Scott. I've taken out the vacuum fulls
> entirely.
> I've now got a nightly vacuum analyze as well as reindex. I'll
> probably
> drop both to every other night.
>
> BTW, the database shrunk by 2 gigs just from reindexing last night.
>
you don't have to reindex too often - it locks exclusively whole
table, just like vacuum full. Just do it every few months, depending
on db growth.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-
242-1444 ext 6379
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: Monday, January 05, 2009 1:37 PM
To: Scot Kreienkamp
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Vacuum problems
On Mon, Jan 5, 2009 at 10:15 AM, Scot Kreienkamp
wrote:
> Scott,
>
&g
Another strategy to look at is to make autovacuum more aggresive by
putting entries for that one table into the pg_autovacuum table. I
know that table exists in 8.3 but I don't remember if it exists in
older versions or how it works there. But if you have that available
you can make that one rela
On Mon, Jan 5, 2009 at 10:15 AM, Scot Kreienkamp wrote:
> Scott,
>
> Would the "alter user postgres set statement_timeout=0;" be a permanent
> change? I ask because our application is using that for its login to
> the database. (No lectures please, I inherited the system that way. I
> already r
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Monday, January 05, 2009 1:05 PM
To: Scot Kreienkamp
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Vacuum problems
"Scot Kreienkamp" writes:
> The nightly vacuums have been working flawlessly, bu
"Scot Kreienkamp" writes:
> The nightly vacuums have been working flawlessly, but about three weeks
> ago the vacuum full started failing. It was taking about 5-10 minutes
> normally, but all of a sudden it started hitting the command timeout
> that I have set, which is at 60 minutes. I thought
t Kreienkamp
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Vacuum problems
On Mon, Jan 5, 2009 at 7:46 AM, Scot Kreienkamp
wrote:
> Hi everyone...
>
>
>
> I have a database that is currently about 25 gigs on my primary DB
server
> running Postgres 8.2.9, and two others that a
On Mon, Jan 5, 2009 at 7:46 AM, Scot Kreienkamp wrote:
> Hi everyone…
>
>
>
> I have a database that is currently about 25 gigs on my primary DB server
> running Postgres 8.2.9, and two others that are less than 1 gig apiece. The
> DB server is a quad proc, quad core, 64 gigs of memory, 5 drive R
ry 05, 2009 11:19 AM
To: Scot Kreienkamp
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Vacuum problems
btw, is that on windows ? (looking at la-z-boy.com, it uses .net).
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
btw, is that on windows ? (looking at la-z-boy.com, it uses .net).
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
well, upgrade to 8.2.11 - even tho, change log doesn't say anything
about vacuum there.
Secondly, I think turn up logging verbosity - and see if postgresql
actually complains about anything there, otherwise it is pretty much
blind guess.
--
Sent via pgsql-general mailing list (pgsql-general@postg
Hi everyone...
I have a database that is currently about 25 gigs on my primary DB
server running Postgres 8.2.9, and two others that are less than 1 gig
apiece. The DB server is a quad proc, quad core, 64 gigs of memory, 5
drive RAID5 array, so it has plenty of horsepower. Until about three
w
On Fri, Jun 01, 2001 at 02:17:17PM +0200, kavoos wrote:
[snip]
> /usr/local/progs/pgsql/bin/postmaster: reaping dead processes...
> /usr/local/progs/pgsql/bin/postmaster: CleanupProc: pid 25501 exited
> with status 139
> Server process (pid 25501) exited with status 139 at Fri Jun 1 13:58:47
> 20
17 matches
Mail list logo
