From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | rohit(dot)guptakec(at)gmail(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #8381: data base inconsistancy |
Date: | 2013-08-14 14:00:08 |
Message-ID: | 20130814140008.GB15089@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sun, Aug 11, 2013 at 08:06:55AM +0000, rohit(dot)guptakec(at)gmail(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8381
> Logged by: Rohit Gupta
> Email address: rohit(dot)guptakec(at)gmail(dot)com
> PostgreSQL version: Unsupported/Unknown
> Operating system: linux
> Description:
>
> Background:- There were a large no. of INSERT/UPDATE/DELETE operation being
> performed on DB. The DB is reindex/vacuum every hour.
> During reindex/vacuum time one of the DB table value was successfully
> updated. But later the read query after ~30 seconds read previous values. Is
> this possible that the update query commit is delayed ? Are there are some
> known issues of commit during reindex/vacuum.
> Currently we are using DB version 8.1
> Later when we check the DB status (after some days)it was having the correct
> updated values.
> We are using default isolation level (Read Committed)
PostgreSQL 8.1 has been unsupported since 2010. Once you've upgraded
to a supported version, if the problem persists, we may be able to
help.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-08-14 21:27:22 | Re: [BUGS] BUG #8335: trim() un-document behaviour |
Previous Message | Curd Reinert | 2013-08-14 11:32:07 | Re: BUG #8382: Duplicate primary key |