Re: BUG #2289: insert into tables not working

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Abhilash Krishnan <abhi_742(at)hotmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2289: insert into tables not working
Date: 2006-03-01 04:05:58
Message-ID: 20060301040558.GA16191@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

[Please copy the mailing list on replies.]

On Wed, Mar 01, 2006 at 08:55:29AM -0800, Abhilash Krishnan wrote:
> ya.... the transactions are commited.... also no error has been shown in any
> of the operations....

How are you determining that data isn't getting inserted? If you
do a select in the same transaction as the inserts, do you see the
data? If you commit the transaction and then start a new transaction,
does a select in the new transaction see the data? If concurrent
transactions aren't able to see the data even after it's committed,
what isolation level are those transactions using? A SERIALIZABLE
transaction won't see data committed by other transactions after
its snapshot has been taken.

If none of this helps then could you post a series of steps that
somebody could use to duplicate the problem?

--
Michael Fuhr

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Adriaan van Os 2006-03-01 13:08:17 BUG #2292: Calling conventions in docs
Previous Message Qingqing Zhou 2006-03-01 03:20:52 Re: FATAL: semctl(1672698088, 12, SETVAL, 0) failed