From: Scott Marlowe <scott.marlowe@gmail.com>
To: Darren Reed <darrenr@fastmail.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Is my database now too big?
Date: Thu, 18 Oct 2007 09:56:05 -0500
Message-ID: <dcc563d10710180756s1a215053n9024ce91b6a6fc63@mail.gmail.com> (raw)
In-Reply-To: <4715FD90.8020607@fastmail.net>
References: <1191730382.18880.1214536197@webmail.messagingengine.com>
<4712E15B.8000405@fastmail.net>
<17093.1192464190@sss.pgh.pa.us>
<4713CA8C.5020303@fastmail.net>
<dcc563d10710151346w430da8a2s265bd8e129ee7d@mail.gmail.com>
<471435D1.4030806@fastmail.net>
<dcc563d10710152103x7b3b2f68q2e133172731f7c0a@mail.gmail.com>
<47145B27.9030200@fastmail.net>
<4715FC35.5020902@fastmail.net>
<4715FD90.8020607@fastmail.net>
On 10/17/07, Darren Reed <darrenr@fastmail.net> wrote:
> Darren Reed wrote:
> > For better or worse, it seems to be behaving itself again for a while...
> >
> > There was, however, one change to my procedure and that was to
> > drop the triggers/functions when restoring the data (using copy into).
>
> Perhaps I spoke too soon...
>
> # /usr/pkg/bin/pg_dumpall -O -U postgres -a > /data/dumpall
> pg_dump: [archiver (db)] connection to database "template1" failed:
> FATAL: out of memory
> DETAIL: Failed on request of size 20.
> pg_dumpall: pg_dump failed on database "template1", exiting
>
> ...for better or worse, I'm interfacing to postgresql using perl's DBI
> interface.
> Are there likely to be any issues from that? (Although I can't see how
> a client
> should be able to cause the server to become corrupt unless there's a bug in
> the server.)
Perl and DBI are fine. You really need to stop using an alpha release
of an OS though. There's no way to know if the problems you're
experiencing are coming from that or something else.
Once you're on a stable OS release, start testing again and let us
know if anything breaks.
But like Tom likes to say, if postgresql breaks running on an alpha OS
release, you get to keep both pieces.
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: scott.marlowe@gmail.com, darrenr@fastmail.net, tgl@sss.pgh.pa.us, jd@commandprompt.com
Subject: Re: Is my database now too big?
In-Reply-To: <dcc563d10710180756s1a215053n9024ce91b6a6fc63@mail.gmail.com>
* 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