Hello.
How bad is this?
2012-08-01 06:30:03 PDT 15961 [local] cp_repository_na2 ERROR: missing
chunk number 0 for toast value 1086399 in pg_toast_987417
2012-08-01 06:30:03 PDT 15961 [local] cp_repository_na2 STATEMENT: VACUUM
(FULL);
Does this mean I have db corruption, or just that the vac
Radovan Jablonovsky wrote:
> We are running PostgreSQL version 9.1.1
You should apply the latest bug fixes by updating to 9.1.4.
http://www.postgresql.org/support/versioning/
> with 32GB of RAM, 32GB of SWAP and during high load we could reach
> (swap + RAM) memory limit.
If you're even
On 25.07.2012 20:15, Joshua D. Drake wrote:
You are going to need to install some HAC components, such as
pacemaker/corosync and automate the base backup creation for the old
master. It is not complicated but it is comprehensive.
I was also looking something like this. Is there any complate
On this issue, instead of going for a newer version of xlc, as suggested, I
opted to get a newer version of the Postgres source code, 9.1.4. After
compiling it with the same xlc version, I found that pg_dump works as expected.
So, the problem appears to be somewhere in the 9.1 source code, at le
Hello.
When running two 'separate' instances of Postgres on the same machine (diff
ports), do I also have two separate installs of the binaries (prefix), or
only two separate datadir ?
If the former, should I make another "postgresb" superuser, or use the same
one?
If I have two separate prefix
On 08/01/2012 12:44 PM, Gary Webster wrote:
Hello.
When running two 'separate' instances of Postgres on the same machine
(diff ports), do I also have two separate installs of the binaries
(prefix),
No
or only two separate datadir ?
Yes
If I have two separate prefix dirs, & only one "pos
Gary Webster writes:
> How bad is this?
> 2012-08-01 06:30:03 PDT 15961 [local] cp_repository_na2 ERROR: missing
> chunk number 0 for toast value 1086399 in pg_toast_987417
> 2012-08-01 06:30:03 PDT 15961 [local] cp_repository_na2 STATEMENT: VACUUM
> (FULL);
If it's repeatable, it's corrupted
I have a lot (maybe 1 every 10 seconds) of this error WARNING: pgstat wait
timeout
Also this
ERROR: canceling autovacuum task
In the pg_stat_activity show an autovacuum process over a very used table
that runs about 1 hour and then this vacuum is cancelled (according to log)
I have
On 08/02/2012 04:27 AM, Anibal David Acosta wrote:
I have a lot (maybe 1 every 10 seconds) of this error WARNING: pgstat
wait timeout
A quick search suggests this can be due to excessive I/O. However, this
thread:
http://postgresql.1045698.n5.nabble.com/pgstat-wait-timeout-td5078125.html
Craig Ringer writes:
> On 08/02/2012 04:27 AM, Anibal David Acosta wrote:
>> I have a lot (maybe 1 every 10 seconds) of this error WARNING: pgstat
>> wait timeout
>>
> A quick search suggests this can be due to excessive I/O. However, this
> thread:
> http://postgresql.1045698.n5.nabble.com/pg
10 matches
Mail list logo