On Wed, 2008-10-15 at 16:05 +0200, Ivan Voras wrote:
> So, pg_start_backup() freezes the data at the time it's called but
> still
> data and xlog are changed, in a different way that's safe to backup?
No, that's not how it works. The pg_start_backup() records the point
that we must rollforward f
>>> "Tory M Blue" <[EMAIL PROTECTED]> wrote:
> psql $DB -c 'vacuum analyze verbose'""
That's fine; you're not using the FULL option.
> every night before I dump
Another thing that could cause bloat is a long-running transaction.
Check for that. If your database is being updated during a
On Fri, Oct 17, 2008 at 10:35 AM, Kevin Grittner
<[EMAIL PROTECTED]> wrote:
> As already pointed out, that's a lot of free space. You don't use
> VACUUM FULL on this database, do you? That would keep the data
> relatively tight but seriously bloat indexes, which is consistent with
> your symptoms
>>> "Tory M Blue" <[EMAIL PROTECTED]> wrote:
> DETAIL: A total of 501440 page slots are in use (including
overhead).
> 501440 page slots are required to track all free space.
> Current limits are: 1087500 page slots, 430 relations, using 6401
kB.
As already pointed out, that's a lot of free sp
On Fri, Oct 17, 2008 at 10:02 AM, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 17, 2008 at 10:47 AM, Tory M Blue <[EMAIL PROTECTED]> wrote:
>> DETAIL: A total of 501440 page slots are in use (including overhead).
>> 501440 page slots are required to track all free space.
>> Current limit
On Fri, Oct 17, 2008 at 10:47 AM, Tory M Blue <[EMAIL PROTECTED]> wrote:
> DETAIL: A total of 501440 page slots are in use (including overhead).
> 501440 page slots are required to track all free space.
> Current limits are: 1087500 page slots, 430 relations, using 6401 kB.
> VACUUM
>
> that look
On Fri, Oct 17, 2008 at 9:30 AM, Kevin Grittner
<[EMAIL PROTECTED]> wrote:
"Tory M Blue" <[EMAIL PROTECTED]> wrote:
>
>> tell me if i should plan upgrades to 8.3.4..
>
> It's a good idea. It should be painless -- drop in and restart.
>
> Make sure that effective_cache_size reflects this.
>
>>> "Tory M Blue" <[EMAIL PROTECTED]> wrote:
> tell me if i should plan upgrades to 8.3.4..
It's a good idea. It should be painless -- drop in and restart.
> After Reindex
> My Indexes
> 1.5G/data/clsindex
>
> After 2 weeks
> My indexes
> 6.8G/data/clsindex
>
> This is 2 weeks. an
Good day,
So I've been running 8.3 for a few months now and things seem good.
I also note there are some bug fixes and you are up to 8.3.4 now, but
reading it I don't see that I'm being affected by anything, but please
tell me if i should plan upgrades to 8.3.4..
The real issue is my index growt
