Alvaro Herrera escribió:
> Also, keep in mind that max_workers is a new setting in 8.3. Since the
> OP is running 8.2, he can only get one "worker". Presumable he needs to
> disable autovac for those two very active tables and setup a cron job to
> process them in their own schedule.
Err, sorry
Scott Marlowe escribió:
> On Tue, Mar 23, 2010 at 5:28 PM, Bhella Paramjeet-PFCW67
> wrote:
> > Hi Scott,
> >
> > Thanks for replying.
> > Can you explain what you mean by increase the number of threads or how I
> > can increase the number of threads? I just have 2 tables that are very
> > activ
On Tue, Mar 23, 2010 at 5:28 PM, Bhella Paramjeet-PFCW67
wrote:
> Hi Scott,
>
> Thanks for replying.
> Can you explain what you mean by increase the number of threads or how I can
> increase the number of threads? I just have 2 tables that are very active. I
> am using postgres version 8.2.7 and
Hi Scott,
Thanks for replying.
Can you explain what you mean by increase the number of threads or how I can
increase the number of threads? I just have 2 tables that are very active. I am
using postgres version 8.2.7 and 3510 storagetek array with 10 disks in raid
1+0.
Thanks
Paramjeet Kaur
we ran into the same problem, had big table, played with vacuum cost and
delay, but can't shrink too much because of heavy insert and delete.
we ended up with using slony for upgrade, also have data copy from fresh
because of inital replication to shrink our large table, with minimum
controlled dow
we ran into the same problem, had big table, played with vacuum cost and
delay, but can't shrink too much because of heavy insert and delete.
we ended up with using slony for upgrade, also have data copy from fresh
because of inital replication to shrink our large table, with minimum
controlled dow
On Tue, Mar 23, 2010 at 2:54 PM, Bhella Paramjeet-PFCW67
wrote:
> Hi All,
>
>
>
> We have a postgres database in which couple of tables get bloated due to
> heavy inserts and deletes. Auto vacuum is running. My question is how can I
> make auto vacuum more aggressive? I am thinking of enabling
>
Hi All,
We have a postgres database in which couple of tables get bloated due to
heavy inserts and deletes. Auto vacuum is running. My question is how
can I make auto vacuum more aggressive? I am thinking of enabling
autovacuum_vacuum_cost_delay and autovacuum_vacuum_cost_limit
parameters. Can
"Dai, Tino" writes:
>>> But having said that, I think 8.1 might generate a reasonable plan if it
>>> weren't getting misled by these useless constraints:
>>> -> Seq Scan on role_setting (cost=0.00..964.50 rows=1 width=70) (actual
>>> time=0.036..121.443 rows=43833 loops=1)
>>> Filter: (((secti
"Steve Jones" writes:
> Issue:the last_vacuum column is not
> being updated following a manual vacuum against a table or database.
It works for me in 8.3 ... as long as there already is a stats entry for
the table in question. You may be running into the pre-9
> 8.2 was released in 2006. 8.1 is going to be desupported entirely at
> the end of 2010. You really need to be holding your vendor's feet to
> the fire about supporting modern versions of Postgres, rather than
> looking for workarounds.
I think that is the correct move.
>> But having said tha
Thanks Brad,
Did you find an alternative connection pooling program that would run on
a AIX install
Cheers
Fran
-Original Message-
From: Brad Nicholson [mailto:bnich...@ca.afilias.info]
Sent: 23 March 2010 15:09
To: Thorne, Francis
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Su
On Tue, 2010-03-23 at 14:05 +, Thorne, Francis wrote:
> Hi all,
>
> I'm looking at installing a connection pooler to work with postgresql
> 8.3, online I have seen both pgbouncer and pgpool II mentioned.
>
> Does anybody know if these are supported on an AIX platform
>
> Thanks
> Frant101
Hi all,
I'm looking at installing a connection pooler to work with postgresql
8.3, online I have seen both pgbouncer and pgpool II mentioned.
Does anybody know if these are supported on an AIX platform
Thanks
Frant101
___
This email is intend
On Tue, Mar 23, 2010 at 7:18 AM, John Lister
wrote:
> Hi, I've successfully set up a slave system using WAL archiving and
> pg_standby, but I have a couple of questions.
>
> I have a couple of questions:
>
> Is it possible to stop the database server (for maintenance for example)
> and resume the
Hi, I've successfully set up a slave system using WAL archiving and pg_standby,
but I have a couple of questions.
I have a couple of questions:
Is it possible to stop the database server (for maintenance for example) and
resume the recovery without starting afresh and making a complete backup o
PostgreSQL Version: 8.3.5
OS Version:FreeBSD 7.0 i386
Issue:the last_vacuum column is not
being updated following a manual vacuum against a table or database.
This was highlighted recently when I configured the check_postgresql.
We had never problems when migrating from 8.1 to 8.2
Problems appear if you migrate to 8.3 or higher (due to explicit
conversions in data types and tsearch changes). But moving from 8.1 to
8.2 should be really easy and shouldn't suppose a problem.
-Original Message-
From: Dai, Tino
To:
We are working with 8.1 and migrating to 8.4
We will see if after migration this behavior has disappeared. ;-)
Thank you, Scott.
-Original Message-
From: Scott Marlowe
To: Iñigo Martinez Lasala
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Bad encoded chars in being inserted
Postgresql version: 8.1.13 (8.1.13-0etch1)
database encoding: UTF-8.
client_encoding: default, that is, it's no set at php level.
However, pg_client_encoding returns "UTF8" as client encoding.
Thank you, Gabriele.
-Original Message-
From: Gabriele Bartolini
To: Iñigo Martinez Lasala
C
20 matches
Mail list logo
