OK. Please run what Tom suggested ( select * from pg_prepared_xacts; ), and
show us output.
Also, please run:
vacuum verbose analyze hotel_site_market;
and also show us output.
depesz
On Tue, Jul 8, 2014 at 2:39 PM, Prabhjot Sheena <
prabhjot.she...@rivalwatch.com> wrote:
> Yes i did ran it
Yes i did ran it in caesius database and not prod01 db that was a typo
there is no long running transactions. i just ran this command select
min(xact_start) from pg_stat_activity where xact_start is not null; to make
sure
Thanks
On Tue, Jul 8, 2014 at 4:43 AM, hubert depesz lubaczewski
wrote:
First question - are you sure you ran vacuum in the correct database? I.e.
in caesius?
Second - is there any long running transaction? select min(xact_start) from
pg_stat_activity where xact_start is not null; should tell you.
depesz
On Tue, Jul 8, 2014 at 12:44 PM, Prabhjot Sheena <
prabhjot.
So this is what i did but my problem is still not going away.
i shutdown the database and started it in single user mode and issued
command vacuum full
The command completed but the issue still exists
The thing i noticed is that whenever i start the database autovaccum
automatically starts on on
John R Pierce writes:
> On 7/7/2014 2:14 PM, Prabhjot Sheena wrote:
>> i will run full vacuum than and see how it goes.
> do make sure there aren't any OLD pending transactions hanging around.
Not only regular transactions, but prepared transactions:
select * from pg_prepared_xacts;
8.3 was
On 7/7/2014 2:14 PM, Prabhjot Sheena wrote:
i will run full vacuum than and see how it goes.
do make sure there aren't any OLD pending transactions hanging around.
if you have any stalled client connections that have left a transaction
open for weeks/months, vacuum can't free any tuples newe
Prabhjot Sheena writes:
> i will run full vacuum than and see how it goes.
I think that is seriously bad advice. It will take longer and not do
anything more to resolve your immediate problem --- which, it appears,
you don't have a whole lot of time to resolve if you want to avoid a
forced shutd
> To: Alvaro Herrera
> Cc: pgsql-ad...@postgresql.org,Forums postgresql
> Subject: Re: [ADMIN] [GENERAL] WARNING: database must be vacuumed within
> 8439472 transactions
>
> While the vacuumdb --analyze command is running i m getting these messages
> for these tables
moved until full vac). I
would recommend it.
Original message From: Prabhjot Sheena
Date:07/07/2014 3:46 PM
(GMT-06:00) To: Alvaro Herrera
Cc: pgsql-ad...@postgresql.org,Forums postgresql
Subject: Re: [ADMIN] [GENERAL]
WARNING: database must be vacuumed within 84
Prabhjot Sheena wrote:
> While the vacuumdb --analyze command is running i m getting these messages
> for these tables which might require full vacuum.
>
> WARNING: relation "public.result" contains more than "max_fsm_pages" pages
> with useful free space
> HINT: Consider using VACUUM FULL on th
While the vacuumdb --analyze command is running i m getting these messages
for these tables which might require full vacuum.
WARNING: relation "public.result" contains more than "max_fsm_pages" pages
with useful free space
HINT: Consider using VACUUM FULL on this relation or increasing the
confi
Prabhjot Sheena wrote:
> Hello
>We are using postgresql 8.3 database for last 5 yrs for this
> production database and its running fine. This is our critical database
> which runs 24*7. This weekend we started getting these messages
>
> HINT: To avoid a database shutdown, execute a full-d
>
> - Mail original -
> De: "Mike Christensen"
> À: "Prabhjot Sheena"
> Cc: pgsql-ad...@postgresql.org, "Forums postgresql" <
> pgsql-general@postgresql.org>
> Envoyé: Lundi 7 Juillet 2014 16:15:18
> Objet: Re: [ADMIN] [GENERAL] WAR
o: Prabhjot Sheena
> Cc: pgsql-ad...@postgresql.org,Forums postgresql
> Subject: Re: [ADMIN] [GENERAL]
> WARNING: database must be vacuumed within 8439472 transactions
> Sounds like you just have to wait until it finishes..
>
>
> On Mon, Jul 7, 2014 at 12:56 PM, Prabhjot Sh
Maybe you can priorize your worker with a ionice?
- Mail original -
De: "Mike Christensen"
À: "Prabhjot Sheena"
Cc: pgsql-ad...@postgresql.org, "Forums postgresql"
Envoyé: Lundi 7 Juillet 2014 16:15:18
Objet: Re: [ADMIN] [GENERAL] WARNING: database m
It does say a FULL vacuum, and that you are not doing.
Original message From: Mike Christensen
Date:07/07/2014 3:17 PM (GMT-06:00)
To: Prabhjot Sheena Cc:
pgsql-ad...@postgresql.org,Forums postgresql
Subject: Re: [ADMIN] [GENERAL] WARNING: database must be vacuumed
Sounds like you just have to wait until it finishes..
On Mon, Jul 7, 2014 at 12:56 PM, Prabhjot Sheena <
prabhjot.she...@rivalwatch.com> wrote:
> Hello
>We are using postgresql 8.3 database for last 5 yrs for this
> production database and its running fine. This is our critical database
Hello
We are using postgresql 8.3 database for last 5 yrs for this
production database and its running fine. This is our critical database
which runs 24*7. This weekend we started getting these messages
HINT: To avoid a database shutdown, execute a full-database VACUUM.
WARNING: database
18 matches
Mail list logo
