Re: Pg_Dumpall error?

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Patrick Hatcher <PHatcher(at)macys(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Pg_Dumpall error?
Date: 2003-07-01 01:11:52
Message-ID: 20030701011152.GL69704@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Forgive the stupid question, since I'm completely unfamiliar with the
logging changes Tom is busy working on, but would it be worthwhile to
have error messages/asserts include a function/filename where the assert
failed? (I'm assuming this is an assert failure). If the assert code
could be easily changed to add that info, it might be helpful to those
not intimately familiar with the code.

Just a thought.

On Mon, Jun 30, 2003 at 03:03:52PM -0700, Patrick Hatcher wrote:
> I've done numerous dumps, but I've never seen this type of error before:
>
> pg_dumpall > datamart.out
> pg_dump: [archiver] could not write to output file (36 != 97)
> pg_dumpall: pg_dump failed on bdc_oz, exiting
>
> Any ideas?
> I'm running Pg 7.3.2
>
> TIA
> Patrick Hatcher
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>

--
Jim C. Nasby, Database Consultant jim(at)nasby(dot)net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard Welty 2003-07-01 01:35:58 oracle->postgresql references
Previous Message Joe Conway 2003-06-30 23:22:52 Re: [HACKERS] Share state ( allocated memory ) across two C functions...