Re: Error in MS Access - Mailing list pgsql-admin

From Joshua D. Drake
Subject Re: Error in MS Access
Date
Msg-id 4468E1B2.60708@commandprompt.com
Whole thread Raw
In response to Re: Error in MS Access  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-admin
Jim C. Nasby wrote:
> On Mon, May 15, 2006 at 12:56:16PM -0500, Xu, Xiaoyi (Rocky) FSM wrote:
>> Thank you Andy.
>>
>> The server is SunOS 5.8 Generic_117350-29 ultra-250. The db is version 7.
>
> 7.what?
>
>> I checked disk (df -k) telling me /home0 is full 100% that has DB on. Former DBA has notes to delete large log files
(server.log).But this time I didn't find same file. I saw pg_log file 4.6 MB timestamped May 9. 
>
> Be *VERY* careful about deleting anything in $PGDATA. A file called
> pg_log is probably safe, but you never know...

Well pg_log is the default logging location of PostgreSQL as of 8.1 (if
it is not logging to syslog), thus anything within there *should* be safe.

However, Jim is correct... be very, very careful in that directory.

>
> 4.6MB certainly isn't going to get you very far. How large is /home0?
> How large is the database? How often have you been vacuuming?


Joshua D. drake


--

            === The PostgreSQL Company: Command Prompt, Inc. ===
      Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
      Providing the most comprehensive  PostgreSQL solutions since 1997
                     http://www.commandprompt.com/



pgsql-admin by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Error in MS Access
Next
From: Simon Riggs
Date:
Subject: Re: does wal archiving block the current client connection?