pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Darren Reed <darrenr+postgres@fastmail.net>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Is my database now too big?
Date: Mon, 15 Oct 2007 22:04:31 -0400
Message-ID: <741.1192500271@sss.pgh.pa.us> (raw )
In-Reply-To: <4714151F.4050307@fastmail.net >
References: <1191730382.18880.1214536197@webmail.messagingengine.com >
<47087723.7040403@commandprompt.com >
<1191744007.14918.1214548241@webmail.messagingengine.com >
<dcc563d10710070114m35df7741tcaa01700b21baec@mail.gmail.com >
<4708A9DC.5060306@fastmail.net >
<dcc563d10710070713q6aa1fbfdqe8f07e5356d39d41@mail.gmail.com >
<47097EA7.902@fastmail.net >
<dcc563d10710071803ia92a046neef1296999173d13@mail.gmail.com >
<4712D97E.7010004@fastmail.net >
<4712E15B.8000405@fastmail.net >
<17093.1192464190@sss.pgh.pa.us >
<4713CA8C.5020303@fastmail.net >
<23809.1192485371@sss.pgh.pa.us >
<4714151F.4050307@fastmail.net >
Darren Reed <darrenr+postgres@fastmail.net> writes:
> Tom Lane wrote:
>> Indeed. And there shouldn't even be anything in MessageContext until
>> the first client command has been received. Maybe you have something
>> in ~/.psqlrc that you haven't told us about?
> That's easy - I don't even have one of these files!
Then the behavior you showed is impossible ;-)
There is *something* that is completely broken about your machine,
and the rest of us really don't have enough context to tell what.
You haven't told us anything about the hardware or operating system,
or how you built or obtained the Postgres executables.
I don't think you should dismiss the possibility of a hardware problem,
especially since the failures aren't 100% reproducible (AFAICT from your
previous remarks). We've seen more than one case where Postgres
stressed a system more than anything else that was being run, and
thereby exposed hardware problems that didn't manifest otherwise.
For instance, a bit of bad RAM up near the end of physical memory might
not get used at all until Postgres starts eating up memory.
Another line of thought is that you built Postgres with a buggy compiler
and thereby got buggy executables. Have you tried running the PG
regression tests?
regards, tom lane
view thread (27+ messages) latest in thread
Message-ID: <741.1192500271@sss.pgh.pa.us>
Permalink: ../741.1192500271@sss.pgh.pa.us/
Also on: postgresql.org/message-id/741.1192500271@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, darrenr+postgres@fastmail.net, scott.marlowe@gmail.com, jd@commandprompt.com
Subject: Re: Is my database now too big?
In-Reply-To: <741.1192500271@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox