The following bug has been logged online:

Bug reference: 1870
Logged by: Sijin MS
Email address: sijin.ms (AT) gmail (DOT) com
PostgreSQL version: v7.3.2-3
Operating system: Redhat 9
Description: Insertion problem
Details:

Dear Sir or Madam:

We are a Software Provider and promoting Linux. Most of our clients are
using Linux. We are using postgres v7.3.2-3 as a backend for our application
software. While inserting data into table, we found that sometime the data
is not inserting into the table and also haven't raise any error messages.
But if we do the same process again then it is inserting into the table
properly.

Sijin M.S
Database Administrator (Linux),
Perfect Software Solutions (clt) Pvt. Ltd.
1st Floor Reshmi Buildings,
Behind S.K Temple,
Kozhikode,
Kerala State,
India - 673001.
Website: www.perfectlimited.com
email : contact (AT) perfectlimited (DOT) com
Mobile : +91 9447392977

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On Fri, Sep 09, 2005 at 08:54:05AM +0100, Sijin MS wrote:
You haven't given us much to go on, but I'll point out that a number
of bugs have been fixed since 7.3.2, some involving data loss.
Those bugs aren't necessarily responsible for the behavior you're
seeing, but you should consider upgrading nonetheless. If you must
stay with 7.3 then consider upgrading to 7.3.10 (the latest). See
the Release Notes for a summary of bug fixes and other changes:

http://www.postgresql.org/docs/7.3/static/release.html

Regarding your application: what language and API are you using?
How do users interface with the application (custom GUI, web browser,
etc.)? How are you checking for errors? Are you sure that the
application *would* detect errors if they occurred (i.e., have you
tested the error checking code by intentionally causing errors)?
Do the server's logs show any error messages? How often does this
happen? Can you duplicate the problem on demand? How long after
the insert are you checking whether the data was inserted? How are
you checking? Could the data have been inserted and then deleted?
Might the inserting transaction have been rolled back? Do you have
any triggers that might be silently discarding the insert?

--
Michael Fuhr

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match