Thank you so much because of your reply i did it a gain but for some tables,
and it works now .!
--
View this message in context:
http://www.postgresql-archive.org/database-is-not-accepting-commands-tp5961831p5962745.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com
It works finally.!
I did vacuum FULL for some tables and Then it just works .!
Maybe as you said this is related to the second part which is commit old
prepared transaction .!
--
View this message in context:
http://www.postgresql-archive.org/database-is-not-accepting-commands-tp5961831p596
On Tue, May 16, 2017 at 1:28 AM, reem wrote:
> We have 1.5 TB database that's shown an error and block all commands.
> The error is :
> "ERROR: database is not accepting commands to avoid wraparound data loss
> in
> database "dbname"
> HINT: Stop the postmaster and use a standalone backend to v
On 05/16/2017 10:44 PM, reem wrote:
postgres 9.3 in ubuntu OS.
Meant to add to previous post.
What is the full version number of Postgres e.g. 9.3.x?
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your su
On 05/16/2017 10:44 PM, reem wrote:
postgres 9.3 in ubuntu OS.
Yes I did this :
1- service postgresql stop
2- /usr/lib/postgresql/9.3/bin/postgres --single -D
/var/lib/postgresql/9.3/main -c
config_file=/etc/postgresql/9.3/main/postgresql.conf dbname
3-vacuum verbose
4- vacumming processed and i
postgres 9.3 in ubuntu OS.
Yes I did this :
1- service postgresql stop
2- /usr/lib/postgresql/9.3/bin/postgres --single -D
/var/lib/postgresql/9.3/main -c
config_file=/etc/postgresql/9.3/main/postgresql.conf dbname
3-vacuum verbose
4- vacumming processed and it shows tables being vacuumed but
The version is 9.3 in ubuntu.
yes i did it in standalone mode by using this command :
//usr/lib/postgresql/9.3/bin/postgres --single -D
/var/lib/postgresql/9.3/main -c
config_file=/etc/postgresql/9.3/main/postgresql.conf dbname/
--
View this message in context:
http://www.postgresql-archive.o
On Tue, May 16, 2017 at 11:03 AM, Adrian Klaver
wrote:
> On 05/16/2017 01:28 AM, reem wrote:
>
>> We have 1.5 TB database that's shown an error and block all commands.
>> The error is :
>> "ERROR: database is not accepting commands to avoid wraparound data loss
>> in
>> database "dbname"
>> HINT
On 05/16/2017 01:28 AM, reem wrote:
We have 1.5 TB database that's shown an error and block all commands.
The error is :
"ERROR: database is not accepting commands to avoid wraparound data loss in
database "dbname"
HINT: Stop the postmaster and use a standalone backend to vacuum that
database.
We have 1.5 TB database that's shown an error and block all commands.
The error is :
"ERROR: database is not accepting commands to avoid wraparound data loss in
database "dbname"
HINT: Stop the postmaster and use a standalone backend to vacuum that
database.
You might also need to commit or roll
On Wed, Apr 6, 2016 at 10:13 AM, pedrovlf wrote:
> Hi,
>
> I'm following error in my DBMS,
>
> < 2016-04-05 17:02:42.053 BRT >ERROR: database is not accepting commands to
> avoid wraparound data loss in database "zabbix"
> < 2016-04-05 17:02:42.053 BRT >HINT: Stop the postmaster and vacuum that
On Wed, Apr 6, 2016 at 8:13 AM, pedrovlf wrote:
> Hi,
>
> I'm following error in my DBMS,
>
> < 2016-04-05 17:02:42.053 BRT >ERROR: database is not accepting commands to
> avoid wraparound data loss in database "zabbix"
> < 2016-04-05 17:02:42.053 BRT >HINT: Stop the postmaster and vacuum that
>
Hi,
I'm following error in my DBMS,
< 2016-04-05 17:02:42.053 BRT >ERROR: database is not accepting commands to
avoid wraparound data loss in database "zabbix"
< 2016-04-05 17:02:42.053 BRT >HINT: Stop the postmaster and vacuum that
database in single-user mode.
I'm running the vacuum in sing
13 matches
Mail list logo
