Skip site navigation (1) Skip section navigation (2)

Re: pg_dump return status..

From: Ian Lance Taylor <ian(at)airs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump return status..
Date: 2001-01-05 22:26:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
ncm(at)zembu(dot)com (Nathan Myers) writes:

> An fprintf returning 0 is a suspicious event; it's easy to imagine 
> cases where it makes sense, but I don't think I have ever coded one.
> Probably >N (where N is the smallest reasonable output, defaulting 
> to 1) may be a better test in real code.

On older systems fprintf returns 0 on success and EOF on failure.

> As I recall, on SunOS 4 the printf()s don't return the number of 
> characters written.  I don't recall what they do instead, and have
> no access to such machines any more.

Probably 0/EOF.  sprintf on SunOS returns its first argument.


In response to


pgsql-hackers by date

Next:From: Ross J. ReedstromDate: 2001-01-05 22:28:07
Subject: bootstrap tables
Previous:From: Nathan MyersDate: 2001-01-05 22:17:09
Subject: Re: pg_dump return status..

pgsql-general by date

Next:From: Tom LaneDate: 2001-01-05 23:01:48
Subject: Re: SHM ids (was running pgsql 7 under Jail'ed virtual machine on FreeBSD 4.2)
Previous:From: Uro GruberDate: 2001-01-05 22:17:29
Subject: PHP and PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group