On Wed, Mar 18, 2009 at 01:18:46AM -0700, Aaron Glenn wrote:
> On Tue, Mar 17, 2009 at 11:27 PM, Scott Marlowe
> wrote:
> start run it's course? for a 35GB+ database how long should I wait? is
> there no way to log the status of what the postgres daemon is actually
> doing while I wait? what's th
On Wed, Mar 18, 2009 at 2:18 AM, Aaron Glenn wrote:
> On Tue, Mar 17, 2009 at 11:27 PM, Scott Marlowe
> wrote:
>> Hard to say with what you've told us so far.
>
> what more should I post/need? I was suspecting that as well as I've
Remember that mentiion of vmstat and top I made in my last post?
On Tue, Mar 17, 2009 at 11:27 PM, Scott Marlowe wrote:
> Hard to say with what you've told us so far.
what more should I post/need? I was suspecting that as well as I've
never had postgres be silent and not work -- I've also never let a db
fill its disk and get f'ed like this. should I just let t
On top of what the other poster said, I'm wondering if you're not
getting any kind of "postmaster not cleanly shutdown, recovery
initiated or something like that when you first start it up. You
don't tend to see a lot of messages after that until recovery is
completed.
What does top and / or vmst
On Tue, 17 Mar 2009, Aaron Glenn wrote:
Despite configuring postgresql.conf for excessive 'verboseness' nothing
gets outputted to syslog or the --log specified file.
You shouldn't trust those destinations for getting really unusual errors
starting the server. Change your log_destination temp
Greetings,
I've gotten myself in a pickle and had a postgresql (8.2) instance
fill its disk completely and shutdown itself down. I've moved the
entire data directory to a new, larger slice however postmaster never
finishes "starting". Despite configuring postgresql.conf for excessive
'verboseness'
