Not that I am aware of.
I must admit, I've needed the "OMG Wrong Command" command myself a few
times over the years.
From: "Burgholzer, Robert (DEQ)"
To: "pgsql-admin@postgresql.org" ,
Date: 12/09/2013 19:27
Subject:[ADMIN] Is there a "Just Kidding" command?
Sent by:
Thanks for the responses folks - I went with the approach that David
mentioned, just chilled out and let the running tasks finish and then
restarted the node. Ultimately, in terms of cost-benefit, I spent 10
minutes watching this process lay out, and only got one email about a
non-responsive app,
I'm on 9.2.4 and I have several databases on the instance say db1, db2,
db2 etc. Today I got this error message on connection of any of the
databases:
ERROR: database is not accepting commands to avoid wraparound data loss
in database "db1"
Suggestion??Stop the postmaster and use a standalone
Rural Hunter wrote
> I'm on 9.2.4 and I have several databases on the instance say db1, db2,
> db2 etc. Today I got this error message on connection of any of the
> databases:
> ERROR: database is not accepting commands to avoid wraparound data loss
> in database "db1"
>Suggestion：Stop the
于 2013/9/14 10:25, David Johnston 写道:
Likely auto-vacuum kicked in and took care of the wraparound issue
while the system was handling your manual vacuum routines...but that
is just a theory
I don't think so. I had to use single connection mode to run the vacuum
full on other dbs.
--
Sent
Rural Hunter escribió:
> I'm on 9.2.4 and I have several databases on the instance say db1,
> db2, db2 etc. Today I got this error message on connection of any
> of the databases:
> ERROR: database is not accepting commands to avoid wraparound data
> loss in database "db1"
> Suggestion：Stop the
Sure. thanks any away and have a good night.
Let me put here the whole scenario:
1. I was called by our application users that all the updating was
failing. So I went to check the db. Any update transaction including
manual vacuum is blocked out by the error message:
ERROR: database is not acce
