Okay, we're finally getting the last bits of corruption fixed, and I finally
remembered to ask my boss about the kill script.
The only details I have are these:
1) The script does nothing if there are fewer than 1000 locks on tables in
the database
2) If there are 1000 or more locks, it will
On Tue, Sep 21, 2010 at 12:57 PM, Sam Nelson s...@consistentstate.com wrote:
On Thu, Sep 9, 2010 at 8:14 AM, Merlin Moncure mmonc...@gmail.com wrote:
Naturally people are going to be skeptical of ec2 since you are so
abstracted from the hardware. Maybe all your problems stem from a
single
Sam Nelson s...@consistentstate.com writes:
Okay, we're finally getting the last bits of corruption fixed, and I finally
remembered to ask my boss about the kill script.
The only details I have are these:
1) The script does nothing if there are fewer than 1000 locks on tables in
the
On Wed, Sep 8, 2010 at 6:55 PM, Sam Nelson s...@consistentstate.com wrote:
Even if the corruption wasn't a result of that, we weren't too excited about
the process being there to begin with. We thought there had to be a better
solution than just killing the processes. So we had a discussion
Hey, a client of ours has been having some data corruption in their
database. We got the data corruption fixed and we believe we've discovered
the cause (they had a script killing any waiting queries if the locks on
their database hit 1000), but they're still getting errors from one table:
On Wed, Sep 8, 2010 at 12:56 PM, Sam Nelson s...@consistentstate.com wrote:
Hey, a client of ours has been having some data corruption in their
database. We got the data corruption fixed and we believe we've discovered
the cause (they had a script killing any waiting queries if the locks on
Sam Nelson s...@consistentstate.com writes:
pg_dump: Error message from server: ERROR: invalid memory alloc request
size 18446744073709551613
pg_dump: The command was: COPY public.foo (columns) TO stdout;
That seems like an incredibly large memory allocation request - it shouldn't
be
It figures I'd have an idea right after posting to the mailing list.
Yeah, running COPY foo TO stdout; gets me a list of data before erroring
out, so I did a copy (select * from foo order by id asc) to stdout; to see
if I could make some kind of guess as to whether this was related to a
single
On Wed, Sep 8, 2010 at 4:03 PM, Sam Nelson s...@consistentstate.com wrote:
It figures I'd have an idea right after posting to the mailing list.
Yeah, running COPY foo TO stdout; gets me a list of data before erroring
out, so I did a copy (select * from foo order by id asc) to stdout; to see
if
Merlin Moncure mmonc...@gmail.com writes:
On Wed, Sep 8, 2010 at 4:03 PM, Sam Nelson s...@consistentstate.com wrote:
So ... yes, it seems that those four id's are somehow part of the problem.
They're on amazon EC2 boxes (yeah, we're not too fond of the EC2 boxes
either), so memtest isn't
My (our) complaints about EC2 aren't particularly extensive, but last time I
posted to the mailing list saying they were using EC2, the first reply was
someone saying that the corruption was the fault of EC2.
Not that we don't have complaints at all (there are some aspects that are
very
I attempted to install 8.0 RC 2 alongside 7.4.5 on my OS X box, but
initdb failed with an error about not enough shared memory.
Remembering that this was a problem for starting two postmasters at the
same time on OS X, I increased the shmmax value to 500 megabytes (I had
seen something say
Jeffrey Melloy [EMAIL PROTECTED] writes:
I attempted to install 8.0 RC 2 alongside 7.4.5 on my OS X box, but
initdb failed with an error about not enough shared memory.
Don't forget that both shmmax and shmall may need attention ... and,
just to confuse matters, they are measured in different
What version of OS X?
Apparently some of the earlier versions did not permit changing this parameter without recompiling the kernel. It seems to have been changed in the more recent versions, though:
http://www.opendarwin.org/pipermail/hackers/2002-August/003583.html
Tom Lane wrote:
Jeffrey Melloy [EMAIL PROTECTED] writes:
I attempted to install 8.0 RC 2 alongside 7.4.5 on my OS X box, but
initdb failed with an error about not enough shared memory.
Don't forget that both shmmax and shmall may need attention ... and,
just to confuse matters, they are
15 matches
Mail list logo
