Return-Path: mao
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA01408; Tue, 18 May 93 09:38:23 -0700
Message-Id: <9305181638.AA01408@postgres.Berkeley.EDU>
From: Mike Olson <mao@postgres.Berkeley.EDU>
Subject: Re: block write errors
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: jaws@pangaea.dme.nt.gov.au's message of 17 May 1993 21:41 PDT
Date: Tue, 18 May 1993 09:38:04 -0700
From: Mike Olson <mao@postgres.Berkeley.EDU>

jaws@pangaea.dme.nt.gov.au (James Woods 61-89-895256) writes:

> cannot write block #(usually 0 or 16) of something_strange [db_name] blind

can you send me the program you're using to write the large objects?
the most common error in using inversion large objects is to forget
to transaction-protect accesses.  that is, you need to do

	res = PQexec("begin");
	fd = p_open(...)
	nbytes = p_write(...);
	nbytes = p_write(...);
	nbytes = p_write(...);
	nbytes = p_write(...);
	nbytes = p_write(...);
	p_close(fd);
	res = PQexec("end");

also, are there any other transactions running concurrently in the
system?
					mike