From: | Mike James <mike(dot)james(at)clutch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Invalid memory alloc request size |
Date: | 2015-08-24 14:27:22 |
Message-ID: | CADeyJsXAZ0bpx3b94sD2GTW8uRH27p3sDh-_98ixXcivgq9cng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Over the weekend, Amazon did some maintenance that resulted in one of our
instances being restarted. Apparently this left the database in a bad
state. This particular instance functions as a slony replication target and
when I went to start up slony, I get the following error message. Here's
some relevant info. The last bit is from the slony log file and it shows
the "invalid memory alloc request size" error. Is there a way to recover
this or do I go ahead and restore from backup?
ubuntu(at)ip-10-90-23-122:~$ psql -U postgres -c "SELECT version();"
PostgreSQL 9.3.5 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2
20080704 (Red Hat 4.1.2-52), 64-bit
(1 row)
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise
2015-08-24 06:50:03 UTC INFO remoteWorkerThread_1: syncing set 1 with 102
table(s) from provider 1
2015-08-24 06:50:33 UTC ERROR remoteWorkerThread_1_1: error at end of COPY
IN: ERROR: invalid memory alloc request size 1970234207
CONTEXT: COPY sl_log_1, line 97033:
[image: Clutch Holdings, LLC] <http://www.clutch.com> Mike James |
Manager of Infrastructure
267.419.6400, ext 204 | mike(dot)james(at)clutch(dot)com201 S Maple St. | Suite 250 |
Ambler, PA 19002
Clutch.com <http://www.clutch.com> | Twitter
<https://twitter.com/clutchsuccess> | LinkedIn
<https://www.linkedin.com/company/2837209> | YouTube
<https://www.youtube.com/user/clutchsuccess> | Clutch Support Center
<http://clientsupport.clutch.com/> The only end to end consumer management
platform that empowers consumer-focused businesses to identify, target,
message, and engage their best customers.
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2015-08-24 14:32:58 | Re: PostgreSQL Developer Best Practices |
Previous Message | David G. Johnston | 2015-08-24 14:09:54 | Re: PostgreSQL Developer Best Practices |