Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm getting the following error in my postgres 8.4 database:

XX000: invalid memory alloc request size 4294967290

Operating System : Windows 7 64 bit Memory : 8GB Database Version: Postgres 8.4 server

I cannot back up my database; I can't even view the data using SELECT. The server gets automatically stopped when I try to do this.

Also posted:

i added the screen shot of the error which occurred during executing the following

select * from < tablename >

enter image description here

ERROR: invalid memory alloc request size 4294967290

          • ERROR * * * * * *

ERROR: invalid memory alloc request size 4294967290

SQL state: XX000


migration rejected from Jun 2 '15 at 18:16

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as off-topic by Max Vernon, Paul White, dezso, Colin 't Hart, RLF Jun 2 '15 at 18:16

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – Max Vernon, Paul White, dezso, RLF
If this question can be reworded to fit the rules in the help center, please edit the question.

"EDB-XX000" suggests that you're actually using EnterpriseDB Postgres Plus or EnterpriseDB Postgres Advanced Server, not PostgreSQL its self. You should really update this with a lot more detail, like the OS you're running on, the message(s) in the logs before the error,etc. – Craig Ringer Mar 1 '13 at 5:05
You should (a) treat this as possible database corruption as per even though it probably isn't, and after that (b) try updating to the latest 8.4.x point release of whatever you're actually using. If that doesn't help, try asking on the EnterpriseDB forums. If you do so, post a link to your EDB forum post here. – Craig Ringer Mar 1 '13 at 5:09
You could've mentioned that you already posted here:… . And that you read and commented on this too: – Craig Ringer Mar 1 '13 at 5:18
Downvoted: Low effort question, missing key information, no info about earlier posts. Will remove downvote if the question is fixed to provide adequate detail and refer to other posts. – Craig Ringer Mar 1 '13 at 5:20
@CraigRinger: Why place the assessment of "low effort" on the poster? Why not just leave it at describing the problem of "missing key information" without judging the person who wrote it? – Andy Lester Mar 1 '13 at 6:02