|
There are no trigger associated with this table. > FYI 8.1 is no longer supported. I understand that. If there are some known related issues, it will be easy to convince, Product mgmt team to upgrade the version of postgresql. Are there known issues related to commit problem in 8.1 version. > Date: Wed, 7 Aug 2013 17:05:59 -0700 > From: adrian.klaver@xxxxxxxxx > To: msq001@xxxxxxxx > CC: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: Commit problem in read-commited isolation level > > On 08/07/2013 04:54 PM, S H wrote: > > Hi, > > > > I have faced very strange problem in one of psotgresql query in one of > > the production environment. It is working fine in development and other > > environment. > > > > Current value in colname = 5; > > Update tablename set colname = 0 where key = 18; > > commit , in parallel to above queries ( either vacuum or reindex of > > table was running) > > > > After 10 sec following query is executed. > > > > select colname from tablename where key = 18 ; > > it is returning old value i.e colname = 5. > > > > After another few seconds > > select colname from tablename where key = 18 ; > > it is returning new value i.e colname = 5. > > I thought the new value is 0? > > > > > > Isolevel level is readcommited. > > Is there any possibility of bug in commit in V8.1 leading to delay of > > commit ? > > Any triggers on the table? > > FYI 8.1 is no longer supported. > > > > > I need to provide explanation of above behavior to my customer. > > > > Regards, > > > -- > Adrian Klaver > adrian.klaver@xxxxxxxxx > > > -- > Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general |
